?

Log in

No account? Create an account
brad's life [entries|archive|friends|userinfo]
Brad Fitzpatrick

[ website | bradfitz.com ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Awake. [Jun. 27th, 2000|11:23 am]
Brad Fitzpatrick
Just got up and guess what? LiveJournal's alive!! Frickin' amazing. Maybe I'll go back to bed or something.
LinkReply

Comments:
[User Picture]From: dweezil
2000-06-27 11:29 am (UTC)

yeah!

go back to bed, dude. You deserve it.
(Reply) (Thread)
[User Picture]From: patrick
2000-06-27 11:34 am (UTC)

sleep now

yay for livejournal now breaking!
(Reply) (Thread)
[User Picture]From: bradfitz
2000-06-27 11:41 am (UTC)

Re: sleep now

s/now/not/;

Yeah ... the big problem I think was that I started running more and more shit as FastCGI processes, but the problem there is that if you don't release your memory (which is difficult in Perl, since you don't even have control over it) your processes swell to start consuming 194MB of memory, then you look at top and notice you're swapping like a motherfucker, using 198MB of swap ... so, I put in a little thing that quitely exit(0)'s every n requests and the problem's solved ..... :-)
(Reply) (Parent) (Thread)
From: (Anonymous)
2000-06-27 01:06 pm (UTC)

Re: sleep now

HACK!! You should use mod_perl - Maybe a little bird will help you rewrite your code for it. Things often feel and look the way you want it to when you're prepared to face the truth, it's finding the truth that's the hard part. In english, I think you know how to fix it, you're just too darn lazy because it requires a lot of work. I'm probably wrong, so be it, just don't come running to me when you file a FixIt! (sorry about the last sentence; it's completely whacked, but it was so smooth!)

Bye for now, back to work for me. Just checking up on my homie bradly.

Yeah, I suck at rap - oh and everything else too.
(Reply) (Parent) (Thread)
[User Picture]From: bradfitz
2000-06-27 01:12 pm (UTC)

Re: sleep now

mod_perl is nice when you have memory. On these boxes, I do not. So FastCGI is ideal.

I'd fix the leaks but the biggest leaks are from DBI and URI. (i.e. not my code). As long as I exit cleanly after serving a request nothing gets dropped and the fcgi process manager just starts a new one.... it's clean. ;)
(Reply) (Parent) (Thread)
From: (Anonymous)
2000-06-27 01:35 pm (UTC)

Re: sleep now

mod_perl uses a little more, if not the same, than FastCGI, but I think in the long run you'll still gain performance. I used to think the same until I actually did some research on it.

Read up on this URL:
http://perl.apache.org/perl_myth.html

And this URL is *awesome* for performance tips:
http://perl.apache.org/guide/performance.html

Note the sections on shared memory. I used to agree with you on the FastCGI vs mod_perl, but after working with mod_perl for the last 6 months and reading up on it, it gets harder and harder to complain about it. Of course what you use is totally up to you, but I think you should switch as soon as possible before further development continues.

Bye for now!
(Reply) (Parent) (Thread)
From: (Anonymous)
2000-06-27 03:59 pm (UTC)

s/now/not

You really are a geek!
(Reply) (Parent) (Thread)
[User Picture]From: bradfitz
2000-06-27 04:00 pm (UTC)

Re: s/now/not

thanks.
(Reply) (Parent) (Thread)