G
George Potemkin
Guest
those times for ixanalys and dbanalys seem pretty bad even for a database that size Tabanalys for the table's area takes 1 hour 44 min. Ixabalys for the index's area takes 40 min. In both cases the proutil is processing approximately 32,000 blocks per sec. Offline dbanalys takes ... 21 hour 20 min. Online dbanalys has completed in 2 hours 24 min (expectedly it's a sum of tabanalys and ixanalys times). The -B value on db startup did not matter. The outputs of both dbanalys commands are exactly the same except of the warning # 2486: [Warning] database in use - reported statistics are approximations. (2486) To find a place where offline dbanalys is spending the most of the time we added timestamps to each line of its output: proutil db -C dbanalys | \ while IFS="" read Line do echo `date '+%H:%M:%S'` "$Line" done dbanalys.log The result of the offline dbanalys: 17:07:20 RM CHAIN ANALYSIS 17:07:20 ----------------- 17:07:20 13:57:04 22675431 block(s) found in the RM chain of Table object 1 Online dbanalys: 18:51:03 RM CHAIN ANALYSIS 18:51:03 ----------------- 18:51:03 18:51:03 22675431 block(s) found in the RM chain of Table object 1 In other words the offline dbanalys spent 20 hours 50 min analyzing the very long RM chain. It processed approximately 302 blocks/sec - a hundred times slower than tabanalys and ixanalys. But it did not report a single word about the results of chanalys. Online dbanalys just instantly reads data from Object Block. Workaround is always to run online dbanalys.
Continue reading...
Continue reading...