Dear developers,
I'm still getting several such messages every day.
I believe most of these *should* be caught by mailman.
Here is one obvious example.
This is with current mailman 2.1.2 , using Python 2.3 - on Solaris 8
Please ask for more details if needed
---BeginMessage---
The attached
Catching up...
On Tue, 2003-08-19 at 18:45, Simone Piunno wrote:
MTAs usually provide a configuration setting to enable cache flush for each
transaction (by use of fsync()), but this is disabled by default because of
the severe impact in performance.
Indeed. I could add an optional flag
At 9:39 AM -0400 2003/09/12, Barry Warsaw wrote:
Indeed. I could add an optional flag to enable fsync'ing in the
_ext_write() calls in Switchboard.py, but I wouldn't want to enable it
by default. It really kills performance.
For 2.1.3, I'll add a flag to Switchboard.py but disable it by
On Fri, 2003-09-12 at 12:28, Brad Knowles wrote:
I would suggest making this flag visible on certain OSes. For
example, turned off by default but visible on Linux, and not even
visible (without hacking) on OSes that don't need it.
Hmm, I don't know what make it visible on some OSs
At 12:56 PM -0400 2003/09/12, John A. Martin wrote:
And, moreover, the choice should depend upon the file system and file
system options. As you know, all Linux boxen do not necessarily only
run ext2 even by distribution default.
It's easy enough to check the type of filesystem to be used,
On Fri, Sep 12, 2003 at 09:58:18PM +0200, Brad Knowles wrote:
At 12:56 PM -0400 2003/09/12, John A. Martin wrote:
And, moreover, the choice should depend upon the file system and file
system options. As you know, all Linux boxen do not necessarily only
run ext2 even by distribution
[Peter C. Norton]
On Fri, Sep 12, 2003 at 09:58:18PM +0200, Brad Knowles wrote:
At 12:56 PM -0400 2003/09/12, John A. Martin wrote:
And, moreover, the choice should depend upon the file system and file
system options. As you know, all Linux boxen do not necessarily only
run ext2 even
On Fri, 2003-09-12 at 17:40, Harald Meland wrote:
Although I haven't done any testing as to how much performance is lost
by fsync(2)ing, I suspect that the sites who actually *need* this lost
performance are (much) more likely to read the upgrade notes than your
average Mailman site admin.
[Barry Warsaw]
Except that when I did some very simple tests, I saw a 97% hit in
performance with fsync turned on.
Ouch. That's pretty severe, all right.
Even though I would *guess* that most casual Mailman sites would
pull through an effective halving of performance without any problems,
On Fri, 2003-09-12 at 12:42, Brad Knowles wrote:
At 12:35 PM -0400 2003/09/12, Barry Warsaw wrote:
Hmm, I don't know what make it visible on some OSs would mean. ;)
So that no hacking is required to make it something the user can
see and modify. We'd still be doing the dangerous
On Fri, 2003-09-12 at 15:58, Brad Knowles wrote:
It's easy enough to check the type of filesystem to be used, and
whether chatter +S has been run on the particular directory
structure.
Maybe there should be a FAQ or README.LINUX items discussing the issue,
and suggesting filesystem
11 matches
Mail list logo
