Re: [AOLSERVER] Mention of AOLserver in Feb 2004 Linux Journal.
Mathopd will have higher latency as an image server, because it is single threaded and doesn't do asynchronous disk I/O. So on a high-end server, the number of IOs/sec it can generate is limited. AS does not have this problem since it is multi-threaded. However, mathopd services requests in a very "fair" manner: in an ab test, the difference between minimum request time and maximum request time is very small. On AS, this is not the case, and there are relatively large variances in request service time, indicating that some threads are being starved. This could be an AS design issue or an OS scheduling/resource issue - dunno. Mathopd is definitely the faster engine, but its design limits its capacity. Mathopd with asynchronous disk I/O would be awesome. Mathopd: Concurrency Level: 15 Time taken for tests: 0.976 seconds Complete requests: 1 Failed requests:0 Total transferred: 2100210 bytes HTML transferred: 450045 bytes Requests per second:10245.90 Transfer rate: 2151.85 kb/s received Connnection Times (ms) min avg max Connect:0 0 1 Processing: 0 0 1 Total: 0 0 2 AOLServer 3.4: - Concurrency Level: 15 Time taken for tests: 1.822 seconds Complete requests: 1 Failed requests:0 Total transferred: 255 bytes HTML transferred: 45 bytes Requests per second:5488.47 Transfer rate: 1399.56 kb/s received Connnection Times (ms) min avg max Connect:0 0 2 Processing: 0 1 210 Total: 0 1 212 > > On Thu, Jan 08, 2004 at 09:15:49PM -0500, Lamar Owen wrote: > > There is a good, if inconspicuous, mention of AOLserver in the Feb LJ. On > > page 46, in the feature on the Magnatune record label, the statement is made: > > "Apache 2 running PHP and OpenSSL serves all the HTML pages. When Magnatune > > was Slashdotted, I found that Apache could not keep up with the load for > > > images. All HTTP image requests now are off-loaded to AOLserver, which had > > the lowest latency to serve images at high speeds." Later: "Mathopd [which > > they use to serve the very large streaming audio files] has more latency than > > AOLserver, which is why we don't use it to serve small images." > > Why would anyone care about the "latency" of serving small images? > Last I heard a human being viewing images in a browser is not exactly > senstive to small latencies the way a parellel MPI program might be, > after all. Or are they talking about absurdly large latency > differences between Mathopd and AOLserver, like several seconds or > more? > > -- > Andrew Piskorski <[EMAIL PROTECTED]> > http://www.piskorski.com/ > -- > AOLserver - http://www.aolserver.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Watch out for Tcl8.4.4+ mem-leaks
Hi ! There are some unwanted mem-leaks in Tcl 8.4.4+ which may cause your server to grow with time. Affected areas are almost all file-related commands, like file, glob, etc. Phew! I am currently going thru the code and correcting those. Specifically, all users of the Tcl_FSGetTranslatedPath() are affected (which means the entire core). I will tell when I'm ready. People experiencing memory-related problems should then go and pick up the last status of the core-8-4-branch from CVS at SF and rebuild the Tcl lib. Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nsd and memory leaks
--- John Shafto <[EMAIL PROTECTED]> wrote: > > Doing what? > This particular machine only has a 512mb of ram, > and serves mostly static content. I have bigger > plans for it though. > > > AOLserver is NOT Apache. Get used to that. > > I'll try to keep them straight. Thanks for the > tip. Am I the only one who feels somewhat uncomfortable by this response? If I've only got 50mb of static content that it's serving up, and then pushing some db stuff through the back, what on earth would possibly make the process use 2gb+? I'd be getting worried then as well... = -- live- http://www.thedenofsin.org/ to- AIM: IMFDUP _-jupiter accepts your offer-_ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nsd and memory leaks
On Fri, Jan 09, 2004 at 11:22:50AM -0800, Nathan Seven wrote: > If I've only got 50mb of static content that it's serving up, and > then pushing some db stuff through the back, what on earth would > possibly make the process use 2gb+? Nothing. I think Dossy was being facetious. Most people using AOLserver are using it for generating dynamic content, and in that scenario AOLserver using 30 to 150 mb or so of RAM is utterly normal and nothing to worry about. You can do things to reduce the memory footprint if you want, but unless it's over a few hundred MB most people don't care, as massive amounts of RAM are so cheap these days. The truly heinous memory leaks in some versions of Oracle's 9i client libraries are the only things I've heard of that, in practice, have ever made AOLserver suck up 1.5+ GB of memory. One user recently reported his AOLserver going up to 1.6 GB for exactly that reason (bad Oracle libraries) before finally crashing due to resource exhaustion on his Linux box. I've never heard of anyone seeing 2 GB or more, although no doubt there are unusual purposes and configurations that could legitimately use that much RAM. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nsd and memory leaks
My personal opinion is that one of the responses to this simple question was pretty shitty, and totally inaccurate. In our experience, an image-serving copy of AOLserver with 30 threads configured runs in about 25MB, regardless of the load, and serving dynamic content on 30 threads takes 100-200MB, depending on the amount of caching you're doing with ns_shares and other types of persistent in-memory data storage, and the size of your preloaded tcl modules library. Of course, if you configure your fastpath cache to be huge or make some other drastic config change in nsd.tcl, it will show up as increased process size. 30 threads is a lot; most sites won't need that, but it all depends on the size of your OS's socket buffers, average size of the content you're serving, etc. An image-serving AOLserver, with TCL disabled, tends to be very stable memory-wise. A dynamic content server tends to grow in our experience, and I've always assumed that's because of heap fragmentation problems - not necessarily leaks. Just restart your server once a day/week. Jim > > --- John Shafto <[EMAIL PROTECTED]> wrote: > > > > Doing what? > > This particular machine only has a 512mb of ram, > > and serves mostly static content. I have bigger > > plans for it though. > > > > > AOLserver is NOT Apache. Get used to that. > > > > I'll try to keep them straight. Thanks for the > > tip. > > Am I the only one who feels somewhat uncomfortable by > this response? > If I've only got 50mb of static content that it's > serving up, and then pushing some db stuff through the > back, what on earth would possibly make the process > use 2gb+? > > I'd be getting worried then as well... > > > = > -- > live- http://www.thedenofsin.org/ > to- AIM: IMFDUP > _-jupiter accepts your offer-_ > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with > the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field > of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] nspostgres.so with AOLserver 4.0
I'm trying to get postgres working with AOLserver 4.0.
config.tcl has the following in it:
ns_section "ns/db/drivers"
ns_param postgres ${bindir}/nspostgres.so
ns_section "ns/db/pools"
ns_param mypool "This pool is for the Postgres Driver"
ns_section "ns/db/pool/mypool"
ns_param driver postgres
ns_param user "postgres"
ns_param datasource "127.0.0.1:32797:postgres"
ns_param connections 2
ns_section "ns/server/${servername}/db"
ns_param pools *
AOLserver 4.0 shows no signs of loading the driver. Is there *any*
documentation on this?
Nate
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
Re: [AOLSERVER] nspostgres.so with AOLserver 4.0
maybe
ns_param nsdb ${bindir}/nsdb.so
On Fri, 2004-01-09 at 16:10, Nathaniel H wrote:
> I'm trying to get postgres working with AOLserver 4.0.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
Re: [AOLSERVER] nspostgres.so with AOLserver 4.0
On Fri, Jan 09, 2004 at 02:10:50PM -0700, Nathaniel H wrote:
> I'm trying to get postgres working with AOLserver 4.0.
> ns_section "ns/db/drivers"
> ns_param postgres ${bindir}/nspostgres.so
> AOLserver 4.0 shows no signs of loading the driver. Is there *any*
> documentation on this?
I think you've named the module wrong, try "nspostgres.so" not
"postgres.so".
If that's not it, some of the OpenACS folks must know, as several of
the lead developers say they've been using AOLserver 4.0 for their
OpenACS development work since around last spring sometime.
Note that the OpenACS 5.0.0 install docs are using AOLserver 4.0:
http://openacs.org/doc/openacs-5-0-0/aolserver4.html
And the AOLserver config.tcl shipped with OpenACS presumably works
properly with either Postgres and Oracle, and either AOLserver
3.3+ad13 or 4.0:
http://cvs.openacs.org/cvs/*checkout*/openacs-4/etc/config.tcl?content-type=text/plain&rev=1.12.2.4
--
Andrew Piskorski <[EMAIL PROTECTED]>
http://www.piskorski.com/
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
Re: [AOLSERVER] nsd and memory leaks
On Fri, Jan 09, 2004 at 12:31:39PM -0800, Jim Wilcoxson wrote: > fragmentation problems - not necessarily leaks. Just restart your > server once a day/week. Which is still quite frequently, and thus very conservative. From what I've heard many people don't restart their AOLservers for months. I tend to schedule mine to restart once a week just to be safe. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nspostgres.so with AOLserver 4.0
Yes that did it thanks!
> maybe
>
> ns_param nsdb ${bindir}/nsdb.so
>
> On Fri, 2004-01-09 at 16:10, Nathaniel H wrote:
>> I'm trying to get postgres working with AOLserver 4.0.
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> <[EMAIL PROTECTED]> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
>
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
Re: [AOLSERVER] nsd and memory leaks
On 2004.01.09, Andrew Piskorski <[EMAIL PROTECTED]> wrote: > On Fri, Jan 09, 2004 at 12:31:39PM -0800, Jim Wilcoxson wrote: > > > fragmentation problems - not necessarily leaks. Just restart your > > server once a day/week. > > Which is still quite frequently, and thus very conservative. From > what I've heard many people don't restart their AOLservers for months. > I tend to schedule mine to restart once a week just to be safe. $ ps -A -olstart,vsz,args | grep dossy.org Sun Nov 16 00:14:54 2003 32512 /home/aolserver/bin/nsd [...] A month and a half without being restarted and it's only 32MB large, AND it's using the supposedly leaky (or unpatched) version of nscgi. Granted, it's not terribly high traffic, but it's certainly stable. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
