Thursday, November 14

Blog

Quick Site Note 2

Load on the server is up with some more sites coming over to Minx; I've assigned more CPU resources to the application, and allocated more threads to the proxy.  We're still peaking at only about 40% of server capacity (plus we have a spare server sitting idle right now), so this not an issue; I just needed to reconfigure the virtual machines to better allocate the hardware resources.

It looks like the proxy was the main problem - when it ran out of threads it would simply drop the HTTP connection.  And I haven't updated the config in two years - the proxy had been running without interruption all that time.

Also, I've installed Redis for improved element caching; I'll bring that into production this weekend.

Update: Redis deployed!  Works nicely.  I was using in-process caching before, and with lazy key evictions and the increased number of worker processes, that was using up a fair bit of memory for a so-so hit rate.  Redis works much better.

Posted by: Pixy Misa at 03:37 PM | Comments (12) | Add Comment | Trackbacks (Suck)
Post contains 171 words, total size 1 kb.

1 Are we on the same server as Ace and the Jawas?

Posted by: Steven Den Beste at Thursday, November 14 2013 04:41 PM (+rSRq)

2 The same physical server, yes.  We were on different virtual servers, but Ace is now moving over to join us.

Posted by: Pixy Misa at Thursday, November 14 2013 05:03 PM (PiXy!)

3 Thanks a lot, everything works great this morning.

Posted by: Pete Zaitcev at Friday, November 15 2013 02:25 AM (RqRa5)

4 FWIW, I got mini-mega-spammed overnight.  I saved an example for you, so you could do ugly things to it.

Posted by: Wonderduck at Sunday, November 17 2013 12:46 AM (Izt1u)

5 Um...  Is it hiding?

Posted by: Pixy Misa at Sunday, November 17 2013 03:09 AM (PiXy!)

6 Yes.  It junked itself, and I was hardly going to dejunkify it.  It's under Edit > comments.

I surely don't mind if you dig around!

Posted by: Wonderduck at Sunday, November 17 2013 07:57 AM (Izt1u)

7

Did something change in how you're displaying the time stamps? Used to be they'd all render in my zone time, for me. But now they seem to be rendering in the owner's zone time. For instance, Wonderduck's time stamps are now all CST. (It was a bit strange leaving a comment there, and seeing the time stamp on my comment two hours in my future.) Your timestamps are all Sydney time.

Was that a deliberate change?

Posted by: Steven Den Beste at Sunday, November 17 2013 09:23 AM (+rSRq)

8 Huh.  Comment timestamps should be in the blog's timezone, not the commenters'.  And the recent changes shouldn't have affected that.

I'll take a look.

Posted by: Pixy Misa at Sunday, November 17 2013 01:17 PM (PiXy!)

9 Wait.  It sounds like it's working how it should.  You mean, all the timestamps on my site are Sydney time, all those on Wonderduck's blog in CST, right?

Posted by: Pixy Misa at Sunday, November 17 2013 01:38 PM (PiXy!)

10 Yes, that's correct. I thought it used to render all the timestamps in the reader's time zone.

Posted by: Steven Den Beste at Sunday, November 17 2013 01:53 PM (+rSRq)

11 Testing caching, don't mind me...

Posted by: Pixy Misa at Sunday, November 17 2013 03:54 PM (PiXy!)

12 Test test...

Posted by: Pixy Misa at Sunday, November 17 2013 03:54 PM (PiXy!)

Hide Comments | Add Comment

Comments are disabled. Post is locked.
49kb generated in CPU 0.0121, elapsed 0.0964 seconds.
56 queries taking 0.0877 seconds, 349 records returned.
Powered by Minx 1.1.6c-pink.