Re^4: POE Question

No, I have nothing to do with that node. I am new to Perl everything.

But I do see what that peron is getting at, if POE reads in only 64k at a time and someone is send a 200k packet. Then POE is needlessly reading ~3 times to do a one time write. Not really efficient.

But then again I know nothing of Perl and really don't understand why the company wants to go this route instead of our traditional Delphi solutions.

Comment on Re^4: POE Question

Replies are listed 'Best First'.
Re^5: POE Question by rcaputo (Chaplain) on Jul 09, 2004 at 22:58 UTC
POE::Driver::SysRW's constructor lets you set the read block size. You can make it as large as sysread() supports. Do realize that reading 200KB at a time means that your program will consume some multiple of that while the data is moving around in memory. Remember to multiply that by the number of concurrent connections you expect. POE::Component::Server::TCP does not expose POE::Driver::SysRW's constructor parameters. It is designed for the 80-90% of applications that don't need special tuning. People writing special-case software are encouraged to use the lower-level modules that offer a lot more tuning: POE::Wheel::SocketFactory (for the TCP server); POE::Wheel::ReadWrite (for the client/server interaction); POE::Filter::Line (which supports many different line separators, or some other filter); and POE::Driver::SysRW (to tune block sizes). You might also want to look at POE::Wheel::ReadWrite's flow control facilities. They'll help tune the memory/buffer size tradeoff on the write side of things. Finally, it's important to remember that these classes are written in Perl. If one doesn't do what you want, subclass it. Or send the author a patch. Or write your own replacements. If they share the core POE::Kernel library, your own classes will work happily beside the ones already written. `-- Rocco Caputo - http://poe.perl.org/`	[reply]

Replies are listed 'Best First'.

Re^5: POE Question
by rcaputo (Chaplain) on Jul 09, 2004 at 22:58 UTC

POE::Driver::SysRW's constructor lets you set the read block size. You can make it as large as sysread() supports. Do realize that reading 200KB at a time means that your program will consume some multiple of that while the data is moving around in memory. Remember to multiply that by the number of concurrent connections you expect.

POE::Component::Server::TCP does not expose POE::Driver::SysRW's constructor parameters. It is designed for the 80-90% of applications that don't need special tuning. People writing special-case software are encouraged to use the lower-level modules that offer a lot more tuning: POE::Wheel::SocketFactory (for the TCP server); POE::Wheel::ReadWrite (for the client/server interaction); POE::Filter::Line (which supports many different line separators, or some other filter); and POE::Driver::SysRW (to tune block sizes).

You might also want to look at POE::Wheel::ReadWrite's flow control facilities. They'll help tune the memory/buffer size tradeoff on the write side of things.

Finally, it's important to remember that these classes are written in Perl. If one doesn't do what you want, subclass it. Or send the author a patch. Or write your own replacements. If they share the core POE::Kernel library, your own classes will work happily beside the ones already written.

-- Rocco Caputo - http://poe.perl.org/

[reply]