How does FTM v16 (top) compare to FTM 2008 (bottom) in some critical computer processes?

Verical grid occurrences except for Disk Time percentage divided by 10

Horizontal grid increments are approximately 4 seconds

 

 

FTM v16 (with 90,000+ individuals, no media)

 

        Open     >>>                                                      Close      >>>>>>

 

 

FTM 2008 v17.0.0.559 (with ONLY 1,900+ individuals  and no media!)

 

        Open    >>>>>>>>>>>>>>>>                     Close            >>

 

                                                LEGEND:

 

                                                            % Disk Time is the percentage of elapsed time that the selected disk drive was busy servicing read or write requests.

 

                                                            % Idle Time is the percentage of time the processor is idle during the sample interval.

 

                                                            % Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring

the duration of the idle thread is active in the sample interval, and subtracting that time from interval duration.  (Each processor has an idle

thread that consumes cycles when no other threads are ready to run). This counter is the primary indicator of processor activity, and displays

the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time that the service is inactive,

and subtracting that value from 100%.

 

Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds

of faults that cause system-wide delays.  It is the sum of Memory\\Pages Input/sec and Memory\\Pages Output/sec.  It is counted in numbers of

pages, so it can be compared to other counts of pages, such as Memory\\Page Faults/sec, without conversion. It includes pages retrieved to

satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.

 

COMMENTS:

 

                        FTM v16 performs as users have experienced – reasonable opening time but with an irritatingly slow and moderate system load closing.  Is that really bad?

work Users want to start ASAP and usually can accept the slower closing time because it is generating a complete backup file!

 

                        FTM 2008 continues to perform dismally bad – even when processing only 2% of what FTM v16 processed!  The high rate of Pages/sec is faults in the file system

cache “usually requested by applications”!  It closes fast but without creating a back-up file.