TestFileOpPerformance   A
last analyzed

Complexity

Total Complexity 16

Size/Duplication

Total Lines 111
Duplicated Lines 0 %

Coupling/Cohesion

Components 1
Dependencies 3

Importance

Changes 0
Metric Value
c 0
b 0
f 0
dl 0
loc 111
rs 10
wmc 16
lcom 1
cbo 3

3 Methods

Rating   Name   Duplication   Size   Complexity  
A __construct() 0 10 1
A execute() 0 9 2
D doPerfTest() 0 88 13
1
<?php
0 ignored issues
show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 32 and the first side effect is on line 24.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2
/**
3
 * Test for fileop performance.
4
 *
5
 * This program is free software; you can redistribute it and/or modify
6
 * it under the terms of the GNU General Public License as published by
7
 * the Free Software Foundation; either version 2 of the License, or
8
 * (at your option) any later version.
9
 *
10
 * This program is distributed in the hope that it will be useful,
11
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
12
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
13
 * GNU General Public License for more details.
14
 *
15
 * You should have received a copy of the GNU General Public License along
16
 * with this program; if not, write to the Free Software Foundation, Inc.,
17
 * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
18
 * http://www.gnu.org/copyleft/gpl.html
19
 *
20
 * @file
21
 * @ingroup Maintenance
22
 */
23
24
error_reporting( E_ALL );
25
require_once __DIR__ . '/Maintenance.php';
26
27
/**
28
 * Maintenance script to test fileop performance.
29
 *
30
 * @ingroup Maintenance
31
 */
32
class TestFileOpPerformance extends Maintenance {
33
	public function __construct() {
34
		parent::__construct();
35
		$this->addDescription( 'Test fileop performance' );
36
		$this->addOption( 'b1', 'Backend 1', true, true );
37
		$this->addOption( 'b2', 'Backend 2', false, true );
38
		$this->addOption( 'srcdir', 'File source directory', true, true );
39
		$this->addOption( 'maxfiles', 'Max files', false, true );
40
		$this->addOption( 'quick', 'Avoid operation pre-checks (use doQuickOperations())' );
41
		$this->addOption( 'parallelize', '"parallelize" flag for doOperations()', false, true );
42
	}
43
44
	public function execute() {
45
		$backend = FileBackendGroup::singleton()->get( $this->getOption( 'b1' ) );
46
		$this->doPerfTest( $backend );
47
48
		if ( $this->getOption( 'b2' ) ) {
49
			$backend = FileBackendGroup::singleton()->get( $this->getOption( 'b2' ) );
50
			$this->doPerfTest( $backend );
51
		}
52
	}
53
54
	protected function doPerfTest( FileBackend $backend ) {
55
		$ops1 = [];
56
		$ops2 = [];
57
		$ops3 = [];
58
		$ops4 = [];
59
		$ops5 = [];
60
61
		$baseDir = 'mwstore://' . $backend->getName() . '/testing-cont1';
62
		$backend->prepare( [ 'dir' => $baseDir ] );
63
64
		$dirname = $this->getOption( 'srcdir' );
65
		$dir = opendir( $dirname );
66
		if ( !$dir ) {
67
			return;
68
		}
69
70
		while ( $dir && ( $file = readdir( $dir ) ) !== false ) {
71
			if ( $file[0] != '.' ) {
72
				$this->output( "Using '$dirname/$file' in operations.\n" );
73
				$dst = $baseDir . '/' . wfBaseName( $file );
74
				$ops1[] = [ 'op' => 'store',
75
					'src' => "$dirname/$file", 'dst' => $dst, 'overwrite' => 1 ];
76
				$ops2[] = [ 'op' => 'copy',
77
					'src' => "$dst", 'dst' => "$dst-1", 'overwrite' => 1 ];
78
				$ops3[] = [ 'op' => 'move',
79
					'src' => $dst, 'dst' => "$dst-2", 'overwrite' => 1 ];
80
				$ops4[] = [ 'op' => 'delete', 'src' => "$dst-1" ];
81
				$ops5[] = [ 'op' => 'delete', 'src' => "$dst-2" ];
82
			}
83
			if ( count( $ops1 ) >= $this->getOption( 'maxfiles', 20 ) ) {
84
				break; // enough
85
			}
86
		}
87
		closedir( $dir );
88
		$this->output( "\n" );
89
90
		$method = $this->hasOption( 'quick' ) ? 'doQuickOperations' : 'doOperations';
91
92
		$opts = [ 'force' => 1 ];
93
		if ( $this->hasOption( 'parallelize' ) ) {
94
			$opts['parallelize'] = ( $this->getOption( 'parallelize' ) === 'true' );
95
		}
96
97
		$start = microtime( true );
98
		$status = $backend->$method( $ops1, $opts );
99
		$e = ( microtime( true ) - $start ) * 1000;
100
		if ( $status->getErrorsArray() ) {
101
			print_r( $status->getErrorsArray() );
102
			exit( 0 );
0 ignored issues
show
Coding Style Compatibility introduced by
The method doPerfTest() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
103
		}
104
		$this->output( $backend->getName() . ": Stored " . count( $ops1 ) . " files in $e ms.\n" );
105
106
		$start = microtime( true );
107
		$backend->$method( $ops2, $opts );
108
		$e = ( microtime( true ) - $start ) * 1000;
109
		if ( $status->getErrorsArray() ) {
110
			print_r( $status->getErrorsArray() );
111
			exit( 0 );
0 ignored issues
show
Coding Style Compatibility introduced by
The method doPerfTest() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
112
		}
113
		$this->output( $backend->getName() . ": Copied " . count( $ops2 ) . " files in $e ms.\n" );
114
115
		$start = microtime( true );
116
		$backend->$method( $ops3, $opts );
117
		$e = ( microtime( true ) - $start ) * 1000;
118
		if ( $status->getErrorsArray() ) {
119
			print_r( $status->getErrorsArray() );
120
			exit( 0 );
0 ignored issues
show
Coding Style Compatibility introduced by
The method doPerfTest() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
121
		}
122
		$this->output( $backend->getName() . ": Moved " . count( $ops3 ) . " files in $e ms.\n" );
123
124
		$start = microtime( true );
125
		$backend->$method( $ops4, $opts );
126
		$e = ( microtime( true ) - $start ) * 1000;
127
		if ( $status->getErrorsArray() ) {
128
			print_r( $status->getErrorsArray() );
129
			exit( 0 );
0 ignored issues
show
Coding Style Compatibility introduced by
The method doPerfTest() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
130
		}
131
		$this->output( $backend->getName() . ": Deleted " . count( $ops4 ) . " files in $e ms.\n" );
132
133
		$start = microtime( true );
134
		$backend->$method( $ops5, $opts );
135
		$e = ( microtime( true ) - $start ) * 1000;
136
		if ( $status->getErrorsArray() ) {
137
			print_r( $status->getErrorsArray() );
138
			exit( 0 );
0 ignored issues
show
Coding Style Compatibility introduced by
The method doPerfTest() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
139
		}
140
		$this->output( $backend->getName() . ": Deleted " . count( $ops5 ) . " files in $e ms.\n" );
141
	}
142
}
143
144
$maintClass = "TestFileOpPerformance";
145
require_once RUN_MAINTENANCE_IF_MAIN;
146