comment on

My web application starting getting significantly slower recently, and after trying a few things (I use Postgres), I tried a VACUUM (secure in the knowledge that I'd been doing a daily VACUUM ANALYZE and this would have no affect).

Heh.

Actually, the VACUUM ran for about 45 minutes, and performance improved by two orders of magnitude. Yep, I had some web pages that were taking 45 seconds to over four minutes to appear .. I'm now back into the 1-3 second range, much more livable.

I've been away from MySQL too long to remember what the equivalent command (if any) is, but don't forget to prod your database into performing well.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

ps 300 classes? Ouch!!!

pps English is not my native language .. your post is better English than I've read from native speakers .. don't worry about that at all.

In reply to Re: OT: Scalable web application architecture by talexb
in thread OT: Scalable web application architecture by badaiaqrandista

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks