Wednesday, August 17, 2005

OraSRP v1.11

Ok, yesterday I failed to parse 1.5Gb trace file with OraSRP v1.10 on Linux machine with 512Mb RAM. It reminds me to some inefficiency in internal data representation.

So, I fixed this problem and released OraSRP v1.11 which succesfully parses that 1.5Gb file.

Also in this version I splitted 'CPU service' pseudo-event into three events: 'CPU service, PARSE calls', 'CPU service, EXEC calls' and 'CPU service, FETCH calls'.

And starting from v1.11 OraSRP shouldn't crash on trace files with malformed lines (this may happens when trace file reached the limit of max_dump_file_size).

Friday, August 05, 2005

OraSRP v1.10

I released OraSRP v1.10

Added printing of 'optimizer goal' info for every statement.

Added <!DOCTYPE> string into html output and changed a little CSS stylesheet.

Added --binds flag: specify maximum number of binds sets to display (1 by default).

It means that from now on OraSRP is able to process bind values in trace files. By default OraSRP displays only most frequent bind values set but you can change it via --bind flag (i.e. when you specify, f.e. --binds=999999, then OraSRP will display all bind values; and if you will specify --binds=0 then OraSRP will just ignore bind values).