So, basically what you say is that if I do something like:
def dataReceived(self, data):
reactor.callInThread(f, data)
and later you have:
def getData():
data = orm_session.query(Object).filter(data).all()
return data # eagerloaded, lazyloaded and put in any format you like
reactor.cal
"Alec Matusis" writes:
> I have tested for bad RAM when the server was installed 3 month ago,
> I did a memtest that run for a day. This is an 8 core server, and I
> run one twistd process per core, and surprisingly, only one crashed
> out of 8. Would you think that the effect of bad RAM would b
I have tested for bad RAM when the server was installed 3 month ago, I did a
memtest that run for a day.
This is an 8 core server, and I run one twistd process per core, and
surprisingly, only one crashed out of 8. Would you think that the effect of bad
RAM would be confined to just once server
Simon,
This is a shot in the dark, but have you tested the twisted performance with
the nagle algorithm disabled?
Travis W Kiel
-Original Message-
From: twisted-python-boun...@twistedmatrix.com
[mailto:twisted-python-boun...@twistedmatrix.com] On Behalf Of Jean-Paul
Calderone
Sent: S
On 07:25 am, matu...@yahoo.com wrote:
Very strange. I am not using any custom C extensions...
In the last two days, it has been under larger load, and it has not
crashed.
I will update to Python 2.6 soon.
Have you tested for bad RAM on that server? The error mode is
sufficiently weird and
Very strange. I am not using any custom C extensions...
In the last two days, it has been under larger load, and it has not crashed.
I will update to Python 2.6 soon.
By the way, are there any gotchas in updating from Twisted-2.5 (custom patched
for epoll bug)/Python 2.4 to Twisted 8.2/Python 2.6
