[Twisted-Python] Twisted Memory Leaks & Epoll
Alec Matusis
matusis at matusis.com
Wed May 2 04:23:05 EDT 2007
Hi Glyph,
> I wonder - have you yet tried this application with current trunk, and did you ever try it with Twisted 2.4?
I have not tried with current trunk or Twisted 2.4.
We are getting another production machine ready with 2.6.18 kernel and Python 2.4.4, and we will migrate that server there within a week from the current 2.6.11 / 2.4.1.
We will try it there both with Twisted 2.2 poll and with 2.5 poll/epoll. I will post the results after we migrate, especially whether epoll is in the edge-triggered or in the level-triggered mode.
From: twisted-python-bounces at twistedmatrix.com [mailto:twisted-python-bounces at twistedmatrix.com] On Behalf Of glyph at divmod.com
Sent: Tuesday, May 01, 2007 8:56 PM
To: Twisted general discussion
Subject: RE: [Twisted-Python] Twisted Memory Leaks & Epoll
Hi Alec,
On 03:40 am, matusis at matusis.com wrote:
>With Twisted 2.5, we saw memory leaks for poll reactor for the same code
>that was non-leaking on 2.2.
I'm sorry we could help you more with that particular leak when it happened. Not that I know of any particular issues that have been fixed since the 2.5 release, but I wonder - have you yet tried this application with current trunk, and did you ever try it with Twisted 2.4?
More information about the Twisted-Python
mailing list