I didn't think this was worthy of a full blog post, but just to keep you informed - on 10-DEC, in an attempt to reduce the amount of RAM used for file caching, the database initialization parameter filesystemio_options was changed from "asynch" to "setall". However, I believe this change was responsible for the slowness you witnessed in the latter part of December. Not only were there a significant number of library cache load lock wait events, but I witnessed the daily workspace purge process go from roughly 30 seconds/workspace purged to over 600 seconds/workspace purged. On 30-DEC, this database initialization parameter was reverted to "asynch" and this certainly has reduced the duration of the workspace purge process as well as improved the overall performance of the database.
Please let me know if further issues are encountered. Thanks.
Thanks for the update Joel
I was using the site yesterday and the only issues I had were with SQL Commands still taking a while to actually load the page and run any statements and also when using the Query Builder (mainly when displaying the list of objects and selecting one for use in the query)
Otherwise, the other pages were only slightly slower than typical - but only by a few seconds, rather than the minute or two as was happening