Alan Runyan wrote:
Do you have anything that is committing very large transactions?
No. In fact; these clients could be running in read only mode. As far
as I'm concerned.
How does data get into the ZEO storage then?
cheers,
Chris
--
Simplistix - Content Management, Zope Python
How does data get into the ZEO storage then?
We have 10 ZEO clients that are for public consumption READ ONLY.
We have a separate ZEO client that is writing that is on a separate box.
The website got slashdoted this morning and we had 4 zeo clients go
out. Basically waiting for the zeo server
Paul Winkler wrote at 2007-4-6 13:30 -0400:
...
If I understand this stuff correctly, the code in question on a
filesystem that *doesn't* have the sparse file optimization would
equate to write N null bytes to this file as fast as possible.
True?
Posix defines the semantics.
I have not looked
Alan Runyan wrote:
The website got slashdoted this morning [...]
Just FYI: Varnish didnt go over 3% CPU during the traffic surge; over
200 req/second.
Off topic: 200 requests a second seems a bit light for a slashdotting,
any more details you can divulge there?
--
Benji York
Senior
On Apr 10, 2007, at 2:19 PM, Alan Runyan wrote:
...
For Jim: We did not adjust the transaction timeout. Would that have
helped in the case of READ's?
Possibly, I'm not sure and I don't have time now to dig. It might be
worth trying, however:
The customer was posting content throughout
Alan Runyan wrote:
We have 10 ZEO clients that are for public consumption READ ONLY.
We have a separate ZEO client that is writing that is on a separate box.
I'd put money on the client doing the writing causing problems.
That or client side cache thrash caused by zcatalog or similar ;-)
The
I'ev not had anything but bad experiences with pound myself, lvs seems a
much more preferable alternative...
We have not had such negative experiences with pound.
data = self.socket.recv(buffer_size)
error: (113, 'No route to host')
That *is* very odd, anything other than pound being
[Tim Peters]
The ZEO client cache is stored in a fixed-size disk file. When a ZEO
client needs to create this file for the first time, it's trying to
ensure there's enough space on disk for it at the start, and reserve
that disk space then, rather than risk dying with a no space left on
device
[Paul Winkler]
Our experiments suggest that ext2, ext3,
and reiserfs optimize for sparse files so there is no such guarantee.
AFAICT from some quick googling and wikipediaing, the same is true
for NTFS, XFS, JFS, ZFS. I suspect we've accounted for the majority
of the production Zope
[Paul Winkler]
...
If I understand this stuff correctly, the code in question on a
filesystem that *doesn't* have the sparse file optimization would
equate to write N null bytes to this file as fast as possible.
True?
[Dieter Maurer]
Posix defines the semantics.
I have not looked it up, but
Alan Runyan wrote:
data = self.socket.recv(buffer_size)
error: (113, 'No route to host')
That *is* very odd, anything other than pound being used for load
balancing or traffic shaping?
This has to be a major problem maker in the system. Pound is simply
round robin connections to pool of
On 10 Apr 2007, at 21:39, Chris Withers wrote:
I'd look at the switches and maybe even the nics and cables :-S
And if you are doing that, also check your network to make sure all
IP addresses are unique.
(..but I'm not a sysadmin.)
And neither am I!
--r
Russ Ferriday - Topia Systems -
12 matches
Mail list logo
