OWC PERFORMANCE OPTIMIZATION TIPS
• Turn off events
The spread sheet contains a bug that causes the stack to overflow when overloading large quantities of data. The workaround works well if no events are monitored during the load process. Otherwise, you will need to reduce the quantity of loaded data. This problem has not been resolved in version 11.
• Calculate on specific range and not entire worksheet. By restricting the range, the recalculation is only performed on items that need recalculation.
• Apply patches and updates to the O.W.C., Internet Explorer, and Windows OS.
• Submit only changed rows to database A significant amount of time may be spent churning through a spreadsheet in order to prepare the contents for the database. Less load can be placed on the database and server resources if only the changed rows are submitted for processing.
• Develop with the latest version of the components when possible.
• Run page in STA model for server-side usage.
Set the aspcompat =true in the document
• Avoid declaring COM objects before page initialization.
With classic ASP as well as scripting languages, the possibility exists to declare and define an instance of a COM object before the page is initialized. This causes server performance issues. Always define your STA COM objects after page initialization.
• Lock on static variables instead of session object because more efficient.
Some times, an application may require data to be persisted so that it may be available for several different requests. When a database will not suffice, you may consider storing the data in the global cache or in the session dictionary. In addition, you may need to protect these objects thru the usual synchronization means. Locking the cache object to prevent rare conditions imposes a wait on all other requests attempting to use the cache object. A more scalable approach would be to wrap the cache object in a class with a static string variable that is less expensive than requesting a lock on the cache object. In this case, the static string represents a lock on the cache object. In this case, the static string represents the availability of the cache object and works well in environments where concurrency is expected to the high.
• Cache values for COM inter op.
• Work with small quantities of data so as not overwhelm the end-user and the rendering process.
• Use concurrent threads to write large rows set of data base when possible.
• Use enumerations instead of dynamic costs that are expensive.
• In memory objects call dispose or set to null for efficiency.
• Write code for Active X browser support and for versions, tailor your code appropriately.
|
No responses found. Be the first to respond and make money from revenue sharing program.
|