Tree Closes Tonight for Mozilla 0.9.9

Tuesday February 19th, 2002 will begin the process to release Mozilla 0.9.9 tonight at 11:59 pm pacific by closing the tree to free checkins. Mozilla 0.9.9 is the last major milestone prior to 1.0, and includes numerous bugfixes in composer, history, and other areas. Along with this, likely new features that will be in the milestone include a new full screen window mode, set image as wallpaper, and composer publishing.

Following the tree close tonight, expect up to a week of tree closure for stability and regression fixes, then a branch to be cut some time next week. As soon as the branch is cut, the trunk will reopen for Mozilla 1.0 checkins. is shooting for a March 1st release date, but due to this being the last milestone before 1.0, and because there is a large amount of code that will be landed tonight prior to tree close, delays may occur.

#62 Re: SQL errors

by macpeep

Thursday February 21st, 2002 12:26 AM

You are replying to this message

"I would have thought the SQL errors would be more related to the SQL server's performance than bandwidth."

You are quite right. But even if your database only allows x amount of concurrent connections, you can very easily set up a queue for those x connections. The code using the database will then block while it waits to get a conncetion, rather than resulting in not getting a connection and having to display an error. The waiting time would be very low or none at all in most cases. Of course all connections would also just be recycled and taken from a pool of connections. That way, the time needed for establishing the connection to the database and logging in is gone.

Another way to get rid of the error is to make sure that each generated page requies a minimal amount of database connections. Since the site isn't really dynamic from one second to the next, data could and should also be cached. For example the "read" counts for each user could be fetched when the user first enters the site and then only kept and updated in memory, and be commited back to the database when the user's session times out. Same for posts. The 10 most recently read article comments could all be cached in memory - after all, they are the same for all users so why fetch and dynamically create the page for them from the database for every request?

I'm sure some - or maybe / hopefully even all - of the suggestions above are actually employed here. If not, they could greatly improve on the performance and reliability of the site. Since the source code for the site isn't open (as far as I know), there's not a lot anyone other than the admin can do, however.