CONTACTS 

SUBJECTS
Performance Slower for SDS Reports than C11
Delayed Screen in SDS, 920725
Help for Slow Performance under W2K, Gordon Jackson
Work M May Improve Slow Performance under W2K, Gordon Jackson
SDS Reports Slow under Windows 3.1
Supersort, Selecting
Macro 120 Process Report Spec
061122 Selection Command File, Configure
Subject, 06112

1311 -    ..
1312 - Summary/Objective
1313 -
131301 - Follow up ref SDS 4 0000, ref SDS 1 0000.
131302 -
131303 - Gordon's letter provides an idea to try specifing a separate drive
131304 - for the work file.  Tried this and did not improve results.
131305 -
131306 - Something is occurring in the selection process that is different from
131307 - sorting, since sorting takes about same time on both machines.
131308 - ref SDS 0 TL4H
131309 -
131310 - Sent a reply with a link to this record showing what has been tried.
131311 -
131312 -
131313 -
131314 -
1314 -
1315 -
1316 - Progress
1317 -
131701 - Received ref DRT 1 0001 from Gordon responding to our telecon on
131702 - 010210... ref SDS 4 TJ4I
131703 -
131704 - Gordon looked at the manual and found the command:
131705 -
131706 -             WORK-DRIVE = M:
131707 -
131708 -        or....
131709 -
131710 -             WORK M
131711 -
131712 - ....where "M" is a mapped drive to use for workspace.
131713 -
131714 - He says that maybe if you force Supersort to use a particular
131715 - workspace it will bypass the "built in Windows 2000 intelligence".
131716 -
131717 -
131718 - The Supersort manual on page III-31 para C-12 says...
131719 -
131720 -     For all sorts except those involving very little data, Supersort
131721 -     makes use of a WORK FILE on disk.  By default, this file is put
131722 -     on the current drive; the user may optionally specify the drive
131723 -     with the command....
131724 -
131725 -
131726 -             WORK-DRIVE = drive
131727 -
131728 -     where drive is a letter, A thru Z, corresponding to a drive
131729 -     present in the system, optionally followed by a colon.
131730 -
131731 -     For example:  WORK-DRIVE = B:
131732 -                   WORK C
131733 -
131734 -     When a large amount of data is being sorted, the user should plan
131735 -     sufficient space for the .work file on one of the disk drives,
131736 -     and specify the drive in a work-drive command.  See "utilization
131737 -     Hints" for furthe discussion.
131738 -
131739 -     When the output disketts change option is invoked the work file
131740 -     must be on a different drive than the output file.
131741 -
131742 -
131743 -                               NOTE
131744 -
131745 -         The work file is called <output filename>.$$$, and is deleted
131746 -         at the beginning of execution and upon successful completion.
131747 -
131748 -
131749 - The next page III-32 para C-13 says....
131750 -
131751 -     The command....
131752 -
131753 -
131754 -             TAGSORT
131755 -
131756 -     causes SORT to use a different internal technique to produce a
131757 -     sorted output file.  The effect is to reduce the work file disk
131758 -     space usage.
131759 -
131760 -     Tagsort is allowed only where there is one sort input file and no
131761 -     merge input files.
131762 -
131763 -     See "Concepts and Facilities" and "Utilization Hints" for further
131764 -     discussoin.
131765 -
131766 - Manual page III-52 in para D-8 says....
131767 -
131768 -     Considerations Relating to Large Sorts
131769 -
131770 -     The amount of data that can be sorted and/or merged is limited by
131771 -     diskette space.  The output file must fie entirely on one
131772 -     diskette.  The work file must also fit entirely on one diskette;
131773 -     however, in most cases it is not bigger than the output file, or
131774 -     can be manipulated (e.g. by using tagsort) to be no bigger than
131775 -     the output file.
131776 -
131777 -     Merging generally uses no work file space; when sorting large
131778 -     amounts of data, the user will want to plan adequate diskette
131779 -     space for the work file.
131780 -
131781 -     In a system with tree or more drives, reserving one drive for the
131782 -     output file and another for the work file generally allows
131783 -     sorting the maximum amount of data.
131784 -
131785 -     In a two-drive system, use one of the following approaches to
131786 -     sorting large amounts of data:
131787 -
131788 -         a.  for sorting one input file only:
131789 -
131790 -             put input file on one drive
131791 -             put output file on one drive
131792 -             put work file on either drive
131793 -             use tagsort
131794 -
131795 -         b.  for any number of sort input files;
131796 -
131797 -             reserve one drive for work file
131798 -             put output file on save drive as input, with
131799 -               diskette change optoin
131800 -             tagsort cannot be used
131801 -
131802 -     Method (b) usually can sort the largest amount od data; but if it
131803 -     yields a "disk full" error for the owrk file (output
131804 -     filename).$$$, try method (a).  Also read the next section on
131805 -     minimizing work file disk space usage.
131806 -
131807 -     Additonal hint:  it is not necessary ot have the SORT program
131808 -     on-line while sorting.  Change disketts after invoking SORT (but
131809 -     before the GO command) in order to make the diskett space the sort
131810 -     program occupies available for data.
131811 -
131812 -  ..
131813 - Based on the foregoing, will try modifying command file as follows...
131814 -
131815 -
131816 -   s i 360 cr;no-r;s e:\sd\08\00000\06\00001;o 1Y001 k-out;no-o;cf 1z
131817 -
131818 - ...where 1z is.....
131819 -
131820 -    se (fi 1 6 bt "990106","991231" or fi 1 6 bt "000101","010205") &
131821 -    and fi 75 88 ="03 00050 01 02" &
131822 -     and fi 15 19 = "00101"
131823 -    k=1 19 220 225 23 24;g
131824 -
131825 -
131826 - Tried this at DOS prompt on on computer 13 (c13) 1.4GHz P4 400 MHz bus
131827 - 46 GB IBM hard drive operating on a 10 MB file under Windows 2000....
131828 -
131829 - Modified command file, per Gordon's idea on 010210. ref SDS 4 Q46G
131830 -
131831 -   C:\09>s cf 1zz
131832 -
131833 - ...where 1zz is.....
131834 -
131835 -    PRI 6
131836 -    i 360 cr
131837 -    no-r
131838 -    s e:\sd\08\00000\06\00001
131839 -    o c:\09\1Y001 k-out
131840 -    work f
131841 -    no-o
131842 -    se (fi 1 6 bt "990106","991231" or fi 1 6 bt "000101","010205") &
131843 -    and fi 75 88 ="03 00050 01 02" &
131844 -     and fi 15 19 = "00101"
131845 -    k=1 19 220 225 23 24
131846 -    go
131847 -
131848 - Results in....
131849 -
131850 -    46419 bytes working storage
131851 -        Sorting...
131852 -            451+0
131853 -    Warning SW5: Insufficient fields or columns for key or select
131854 -                 in one or more records, blanks assumed
131855 -
131856 -    99567 records input for sort
131857 -        99116 sort records excluded or not selected
131858 -    451 records sorted
131859 -    Output file size 13079 bytes
131860 -    1 sort run
131861 -
131862 -    Sort/merge completed in 13 seconds.
131863 -
131864 -
131865 -
131866 - Same run at DOS prompt on computer 12 (c12) 650MHz P3 100 MHz bus 12
131867 - GB slow notebook computer hard drive under Windows 2000....
131868 -
131869 -    46419 bytes working storage
131870 -        Sorting...
131871 -            450+0
131872 -    Warning SW5: Insufficient fields or columns for key or select
131873 -                 in one or more records, blanks assumed
131874 -
131875 -    99488 records input for sort
131876 -        99038 sort records excluded or not selected
131877 -    450 records sorted
131878 -    Output file size 13050 bytes
131879 -    1 sort run
131880 -
131881 -    Sort/merge completed in 1 seconds.
131882 -
131883 - We get same results with another computer, PIII 850MHz 100 MHz bus,
131884 - and 12 GM hard drive running w2k.  It does this op in 1 second.
131885 -
131886 - How can we get the faster 1.4 GHz computer to at least equal the
131887 - production of the slower machines?
131888 -
131889 -    Note:
131890 -
131891 -       Tried changing from sort to merge, because the file is already
131892 -       sorted....
131893 -
131894 -            m e:\sd\08\00000\06\00001
131895 -
131896 -       ...then the routine executes, but get OS crash that says...
131897 -
131898 -            Memory allocation error
131899 -            Cannot load COMMAND, system halted
131900 -
131901 -  ..
131902 - Without the selection spec, so the file is only sorted, produces
131903 - following results on c13.....
131904 -
131905 -    C:\09>s cf 1xx
131906 -    46524 bytes working storage
131907 -     Sorting...
131908 -         1367+1790    1367+824    1367+1539    1367+1369
131909 -         1367+2913    1367+1117    1367+1523    1367+686
131910 -         1367+734    1367+1711    1367+1321    1367+1921
131911 -         1367+1633    1367+1338    1367+1525    1367+1685
131912 -         1367+819    1367+1180    1367+1908    1367++1502
131913 -         1366+723    1366+2136    1366++6313    1365+2353
131914 -         1365+821    1365++4381    1364+581    1364+863
131915 -         1364+1405    1364++1983    1363+1296    1363+1138
131916 -         1363++524    934+0
131917 -     Merging...
131918 -         34
131919 -    Warning SW5: Insufficient fields or columns for key or select
131920 -                 in one or more records, blanks assumed
131921 -
131922 -    99567 records sorted
131923 -    Output file size 2887443 bytes
131924 -    34 sort runs    1 merge run    Work file disk space usage 2688309
131925 -    bytes
131926 -
131927 -    Sort/merge completed in 3 seconds.
131928 -
131929 -
131930 - On slower c12 notebook computer, same change gives same results,
131931 - except it only takes 1 second.
131932 -
131933 - If we could get c13 to do the sort and selection in 3 seconds instead
131934 - of 13 seconds that would be helpful.
131935 -
131936 -
131937 -
131938 -
131939 -
131940 -
131941 -
131942 -
131943 -
131944 -
131945 -
131946 -