Performance Hints

Performance Hints

Java: Always use the latest 1.6 Java available.
Memory: Always pass enough memory on the launch script. SQLBrowser is greedy. Especially for Batch Analysis. See Command Line to see how to add memory.
Local Drive: Always install sqlbrowser on a local drive.If you install on a shared drive, use the sqlbrowser_shared.cmd provided in the bin directory which copies the distribution to the local drive. (Class loading from a network drive is slow). See the Installation section for more information.
Remove 'Auto Analyze Source Files' option in Options / General if you find that it eats too much resources
Anti-virus: Batch Analysis produces a lot of files. Exclude SQLBrowser output directory from the antivirus write scans if applicable.
Update Stats on System Tables: SQLBrowser reads a lot from system tables. On ASE 15, it is sometimes necessary to run manual 'update statistics' on system tables (!) to speed up sqlbrowser. This was not necessary in V12.5.
Subversion: When linked with SVN, SQLBrowser can be slow to start. This is because of the number of SVN stats it launches (when either opened files are under SVN or favorties point to SVN dirctories)

Monitoring Throttling

To avoid sqlbrowser monitor taking too much resource on the server you can act on 3 parameters: (Options/Monitor)

Set the ‘sleep time’ to more than 1 second
Set the ‘stop after N iterations’, to avoid it running unattended
Untick the ‘Show Locks’ in the Option/Monitor Panel. If many row-level locks are used, this can help a lot