> On Mar 4, 2015, at 8:59 AM, Al Niessner wrote:
>
> Nevermind. While building the test case I figured out where I went wrong.
... and that right there is exactly why we request that those asking questions
build those types of examples ;-D
> I had a subprocess pool that I forgot to close and
Nevermind. While building the test case I figured out where I went wrong. I
had a subprocess pool that I forgot to close and it just grew out of hand.
I checked and twisted is running at 4 processes. Sounds better.
Thanks for all of the help.
On Mon, Mar 2, 2015 at 1:50 PM, Glyph Lefkowitz
wrot
I am new to twisted so the start up is really those two lines, but I can
work at a minimal reproducers. May take a day or two.
I read through the bug report a bit and there seems to be some funny stuff
with the deferToThread and a possible race condition, Did I read that
correctly?
The other prob
> On Mar 2, 2015, at 10:36 AM, Al Niessner wrote:
>
>
> Platform:
> CPU: Intel (2x with 8 core each then hyper-threading gets us to 32 virtual)
> Ubuntu 14.04
> Python 3.4 (yes, I know)
> Twisted 13.2.0
>
> I use the vanilla twisted.internet.reactor.run() with the factory
> twisted.web.server.
Platform:
CPU: Intel (2x with 8 core each then hyper-threading gets us to 32 virtual)
Ubuntu 14.04
Python 3.4 (yes, I know)
Twisted 13.2.0
I use the vanilla twisted.internet.reactor.run() with the
factory twisted.web.server.Site(root). It all runs just fine (seemingly)
but,when I was snooping arou
