alierak: (Default)
[personal profile] alierak
I previously noted an apparent memory leak in several workers under Perl 5.14.2. We upgraded the Encode module because it had a known memory leak bug and seemed relevant, and that did actually slow down the memory leak somewhat. However, I now need help brainstorming what could still be causing this. The affected workers seem to be synsuck, send-email, and resolve-extacct, so I've set cron jobs to restart those every so often.

Honestly, what can resolve-extacct be doing that causes it to grow to 9GB in size over the course of a week? We will probably have to resort to profiling memory usage to figure this one out.
foxfirefey: A guy looking ridiculous by doing a fashionable posing with a mouse, slinging the cord over his shoulders. (geek)
[personal profile] foxfirefey
So, I've been doing some heavy web page optimization at my day job and on a whim I ran an analyzer on some DW pages and found what I think could be a very easy-to-make-happen optimization: we're not gzipping the JS/CSS static files when we serve them.


* The new entry page: 221.2KiB (70% reduction) -- quite the savings when the entire bundle is 349.9 KB
* My reading page: 149.3KiB (68% reduction) -- when the total page is 541.5 K, so decent

Would this be as easy to set up as I think it would, or are there other reasons not to do it?
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
Currently, the sphinx indexer works by looping over users and copying news and edited entries into the sphinx database. Those copies are scheduled periodically using bin/schedule-copier-jobs, and also per-user when entries are created or edited. But in the latter case, the copier still searches the whole log2 table for that user's entries instead of only copying the affected entry. Does anyone know what the cost of that is compared to the indexing itself? If it's significant, may also be used to trigger per-entry copying. Anyone has performance/resource use figures, or opinions?
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
I'm really interested in learning more about what kind of performance things we need to keep in mind while coding, and how to design for a well-behaved high-availability web app. I know the very basics, like using memcache whenever possible and using direct assignments instead of shifts, but not much else!

So, is anyone interested in writing tutorials on things to keep in mind when coding stuff for performance factors? As we grow, this is going to start to be stuff we should keep in mind, and I think it's a great opportunity for us all to share knowledge and learn together. No matter how much you know, even if you think it's not much, it's probably more than someone else (ie, me) knows...


dw_dev: The word "develop" using the Swirly D logo.  (Default)
Dreamwidth Open Source Development

April 2019



RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Apr. 24th, 2019 06:59 am
Powered by Dreamwidth Studios