AOLserver Chat Logs

2005/10/10

IRC [00:16] *** holycow joined the chat.
IRC [02:53] *** holycow parted the chat.
IRC [09:12] *** holycow joined the chat.
IRC [10:15] *** holycow parted the chat.
IRC [10:16] *** holycow joined the chat.
IRC [10:42] *** holycow parted the chat.
IRC [10:43] *** holycow joined the chat.
IRC [11:26] *** holycow parted the chat.
IRC [11:27] *** holycow joined the chat.
IRC [12:25] <Peaceful> ooo, wiki's lookin nice
IRC [12:27] <Peaceful> content is pretty sparse, though. Where can I find the docs for nspostgres? Wiki page about it doesn't have much.
IRC [12:47] <Dossy> :)
IRC [12:47] <Dossy> google might know. if it does, teach the wiki :)
IRC [12:49] <Dossy> nelson: you moved to NYC from TX?
IRC [12:49] <Dossy> oops, wrong window :P
IRC [12:49] <Peaceful> Ya, tried google. It knows about the download and the wiki and some debian packages of it.
IRC [12:50] <Peaceful> I checked the tarball, no docs in there.
IRC [12:50] <Peaceful> Maybe there's a more general aolserver option that could fix my problem
IRC [12:51] <Peaceful> I have a page that uses a specific db pool.
IRC [12:52] <Dossy> what "docs" are you looking for?
IRC [12:52] <Peaceful> It got real popular, and it started hanging for what I assume is db contention (cpu on webserver and db are both minimal)
IRC [12:52] <Peaceful> Configuration docs
IRC [12:52] <Dossy> configuration of /what/ though?
IRC [12:52] <Dossy> perhaps you are running out of db connections, and you're not specifying any timeout on ns_db
IRC [12:53] <Dossy> (which, I think, means "infinite timeout" :)
IRC [12:53] <Peaceful> That's what I thought, so i....
IRC [12:53] <Peaceful> infinite timeout?
IRC [12:53] <Peaceful> that could be it
IRC [12:53] <Peaceful> I tried boosting connections from 4 to 12 to 16 to 32 without any effect
IRC [12:53] <Peaceful> but I haven't played with timeout
IRC [12:54] <Peaceful> somethinge like 'ns_param timeout 60'?
IRC [12:56] <Dossy> no, it's on the ns_db call itself.
IRC [12:56] <Dossy> although we might have hacked in a server-wide timeout config in recent 4.x
IRC [12:56] <Peaceful> So where/how do I set it. I just checked the db admin page on aolserver.com and it's got nothing about timeouts
IRC [12:57] <Dossy> yeah, timeout is per-ns_db call, it looks like.
IRC [12:57] <Dossy> ns_db -timeout $time
IRC [12:57] <Peaceful> ah, cool
IRC [12:58] <Peaceful> I see it. http://aolserver.com/docs/devel/tcl/api/db.html#ns_db
IRC [12:58] <Peaceful> Didn't think to look at runtime stuff
IRC [12:59] <Peaceful> Hmm...that's how long a page will wait for a handle to be available, though.
IRC [13:01] <Dossy> holy wow. nelson, why didn't I find out about your blog earlier?
IRC [13:02] <Dossy> holy wow. nelson, why didn't I find out about your blog earlier?
IRC [13:02] <Dossy> crap, wrong window - and then pasted to the same wrong window. d'oh :P
IRC [13:02] <Dossy> right.
IRC [13:17] *** holycow parted the chat.
IRC [13:58] *** hagna joined the chat.
IRC [13:59] <hagna> Can aolserver tell me what db pools are being used?
IRC [13:59] <hagna> it seems like there is contention for pools
IRC [14:00] <hagna> Dossy: ping
IRC [14:16] <Dossy> ?
IRC [14:17] <Dossy> "being used"?
IRC [14:17] <hagna> gethandle takes a while to return
IRC [14:17] <Dossy> yeah.
IRC [14:17] <Dossy> you want pool stats? dunno ...
IRC [14:18] <hagna> trying to isolate the db or aolserver
IRC [14:18] <hagna> as the source of the problem
IRC [14:19] <Dossy> DB should be able to tell you how many clients are connected ...
IRC [14:20] <Dossy> unfortunately, there's no [ns_db stat] or [ns_db info] ...
IRC [14:20] <Dossy> yeah, being able to get "# of handles allocated" and "total # of handles" for a pool woudl be /really/ useful. :)
IRC [14:20] <Dossy> you could hack it into your copy (you have the source!) and see if it tells you anything useful.
IRC [14:21] <hagna> hmm well the db machine is 0 idle so it must be the db
IRC [14:23] <Dossy> heh
IRC [14:58] <hagna> ok so if aolserver is doing expensive ns_db selects and then I kill the server is it crazy to assume that those queries are still going on on the database machine or do they all get cancelled?
IRC [15:49] *** BSDork joined the chat.
IRC [16:49] *** holycow joined the chat.
IRC [17:42] *** BSDork parted the chat.
IRC [18:24] <Dossy> hagna: typically, they continue to execute inside the database server unless you kill the sessions at the database directly.
IRC [18:34] <hagna> ok
IRC [18:41] <hagna> yo
IRC [18:42] *** Mooooooo joined the chat.
IRC [19:03] *** holy_cow joined the chat.
IRC [19:17] *** holycow parted the chat.
IRC [19:44] *** hagna parted the chat.
IRC [19:59] *** holycow parted the chat.
IRC [20:11] *** holycow joined the chat.
IRC [20:39] *** holycow parted the chat.
IRC [23:40] *** holycow joined the chat.
IRC [23:52] *** Mooooooo parted the chat.