Forum OpenACS Q&A: PostgreSQL Reliability on Windows 2000
on Windows 2000? For political reasons we can't use Linux But we
definitely need our platform to be rock solid. It will be doing
nothing but run the database, but will need to be able to handle
about 8 inserts/second and 5 queries/second (its a decently powerful
machine, 1ghz/1gb ram/scsi).
I would guess that your performance requirements are on the high end of doable but that's just a guess. If you had problems it would almost certainly be with the inserts.
got OACS and the custom app we've developed for them up and
running, but postgresql was never stable enough to deploy -
whenever we tried to import the data from their old system PG
would start dying with shared memory errors. Adding a .25
second delay between record insertions let us get the system
fully loaded, but we'd see the same database crashes whenever
we stressed the system.
Personally, I'd be very wary of running PG under production loads
on windows, but perhaps that's just me...
enough memory, but that the shared memory segments had
been corrupted. We did try (among other things) increasing
shared_buffers, which didn't as far as I recall make any
I wonder if we were perhaps hitting some limit in cyg_ipc wrt the
amount of shared memory it can support... hmm...
Besides (assuming you want to use OACS as well), you'd be facing at least 2 more problems with W2K/PostgreSQL/AOLServer: (a) support issue (as you know, AOL folks no longer support Windows version of AOLServer); (b) some functionality on AOLServer side would be missing and/or not working well.
For example of a (b), I could never get binary file uploads to work well on Windows/AOLServer combination (but that was about a year back with OACS 3.2.5 and on NT).
I do think that cygipc (http://www.neuro.gatech.edu/users/cwilson/cygutils/index.html) is the weakest link in the chain right now. It will get rolled into the forthcoming "Cygwin Daemon" but is currently deprecated by the author.
If you end up doing any benchmarking, I would love to see the results! My PostgreSQL 7.1.3/Cygwin OpenACS site is not experiencing 8 inserts/second, but it would be great if it could.
I'm not sure I completely grasp Matthew's situation - can you say what the political reasons are? Is MacOS X a possibility? How are you going to be connecting to PostgreSQL? Is this for an OpenACS installation?
Did the support for extended parser has been restored in AOLServer 4 since (i.e. is anyone able to run OpenACS 4.x on unmodified AOLServer 4)?
the 6.3.x that was current in late '98...
In late December, the adp parser was rewritten to minimize duplicate overhead of per-thread bytecode caches. In the past few days it has had a few more changes. Registered tags can now be modified after startup. There are some new commands like ns_adp_safeeval, which blocks open <% ... %> scripting. I haven't tried out this newer code with OpenACS yet, but I don't think it will cause problems.