Did this article resolve your question/issue?



The "proutil bigrow"command performs differently between 2 different disks types

« Go Back


TitleThe "proutil bigrow"command performs differently between 2 different disks types
URL NameThe-proutil-bigrow-command-performs-differently-between-2-different-disks-types
Article Number000177926
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: Linux
Question/Problem Description
The "proutil bigrow"command performs differently between 2 different disks types. It takes longer on the Intel card. Is this expected?
A probkup, prorest and even dbanalys takes the same amount of time, regardless of the drive used.

Steps to Reproduce
Clarifying Information
Virtual machine environment. 
Error Message
Defect/Enhancement Number
The difference between bigrow and the other tools is that bigrow is pre-allocating and re-formatting disk space specified by the command. If there is a difference in performance between disks, it is because one disk has a better I/O then the other. A test outside of Progress can be performed to eliminate Progress involvement. 

For example, if specifying 8 in the bigrow command and the BI cluster size is 16Mb, that means the BI file is being pre-formatted to (8+4) * 16Mb = 192Mb. The 4 represents the default BI clusters. On unix/linux run the dd command to simulate what bigrow does:

/usr/bin/time dd if=/dev/zero of=/tmp/test.out bs=<bi block size> count=<value> oflag=dsync

The BI block size can be acquired from the output of the command "proutil <dbname> -C describe"
For the example above, the count should be a number that multiplied by the BI block size will get a file that is 192Mb in size, for example if the BI block size is 8k then the command should be :

/usr/bin/time dd if=/dev/zero of=./test.out bs=8k count=24550 oflag=dsync
Last Modified Date12/13/2018 5:09 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.