- SEE ALSO
- COPYRIGHT AND LICENSE
POE::Devel::Benchmarker - Benchmarking POE's performance ( acts more like a smoker )
perl -MPOE::Devel::Benchmarker -e 'benchmark()'
This package of tools is designed to benchmark POE's performace across different configurations. The current "tests" are:
- session creation
- session destruction
- select_read toggles
- select_write toggles
- POE startup time
This module is poorly documented now. Please give me some time to properly document it over time :)
Here's a simple outline to get you up to speed quickly. ( and smoking! )
- Install CPAN package + dependencies
Download+install the POE::Devel::Benchmarker package from CPAN
apoc@apoc-x300:~$ cpanp -i POE::Devel::Benchmarker
- Setup initial directories
Go anywhere, and create the "parent" directory where you'll be storing test results + stuff. For this example, I have chosen to use ~/poe-benchmarker:
apoc@apoc-x300:~$ mkdir poe-benchmarker apoc@apoc-x300:~$ cd poe-benchmarker apoc@apoc-x300:~/poe-benchmarker$ mkdir poedists apoc@apoc-x300:~/poe-benchmarker$ mkdir results apoc@apoc-x300:~/poe-benchmarker$ cd poedists/ apoc@apoc-x300:~/poe-benchmarker/poedists$ perl -MPOE::Devel::Benchmarker::GetPOEdists -e 'getPOEdists( 1 )' ( go get a coffee while it downloads if you're on a slow link, ha! )
- Let 'er rip!
At this point you can start running the benchmark!
NOTE: the Benchmarker expects everything to be in the "local" directory!
apoc@apoc-x300:~$ cd poe-benchmarker apoc@apoc-x300:~/poe-benchmarker$ perl -MPOE::Devel::Benchmarker -e 'benchmark()' ( go sleep or something, this will take a while! )
This module exposes only one subroutine, the benchmark() one. You can pass a hashref to it to set various options. Here is a list of the valid options:
- litetests => boolean
This enables the "lite" tests which will not take up too much time.
- quiet => boolean
This enables quiet mode which will not print anything to the console except for errors.
As the Benchmarker goes through the combinations of POE + Eventloop + Assertions + XS::Queue it will dump data into the results directory. The Analyzer module also dumps YAML output in the same place, with the suffix of ".yml"
Please look at the POE::Devel::Benchmarker::Analyzer module.
This section will explain the miscellaneous questions and preemptively answer any concerns :)
Simply delete it from the poedists directory. The Benchmarker will automatically look in that and load POE versions. If you wanted to test only 1 version - just delete all directories except for that one.
Keep in mind that the Benchmarker will not automatically untar archives, only the Benchmarker::GetPOEdists module does that!
This isn't implemented yet. As a temporary work-around you could uninstall the POE::Loop::XYZ module from your system :)
Why would you want to? That's the whole point of this suite!
This will be added to the module soon. However if you have the time+energy, please feel free to dig into the YAML output that Benchmarker::Analyzer outputs.
This isn't implemented yet. You could always manually delete the POE versions that was tested and proceed with the rest.
Automatically exports the benchmark() subroutine.
- Perl version smoking
We should be able to run the benchmark over different Perl versions. This would require some fiddling with our layout + logic. It's not that urgent because the workaround is to simply execute the smoke suite under a different perl binary. It's smart enough to use $^X to be consistent across tests :)
- Select the EV backend
<Khisanth> and if you are benchmarking, try it with POE using EV with EV using Glib? :P <Apocalypse> I'm not sure how to configure the EV "backend" yet <Apocalypse> too much docs for me to read hah <Khisanth> Apocalypse: use EV::Glib; use Glib; use POE; :)
- Disable POE::XS::Queue::Array tests if not found
Currently we blindly move on and test with/without this. We should be smarter and not waste one extra test per iteration if it isn't installed!
- Be smarter in smoking timeouts
Currently we depend on the litetests option and hardcode some values including the timeout. If your machine is incredibly slow, there's a chance that it could timeout unnecessarily. Please look at the outputs and check to see if there are unusual failures, and inform me.
Also, some loops perform badly and take almost forever! /me glares at Gtk...
- More benchmarks!
As usual, me and the crowd in #poe have plenty of ideas for tests. We'll be adding them over time, but if you have an idea please drop me a line and let me know!
dngor said there was some benchmarks in the POE svn under trunk/queue...
I want a bench that actually tests socket traffic - stream 10MB of traffic over localhost, and time it?
- Add SQLite/DBI/etc support to the Analyzer
It would be nice if we could have a local SQLite db to dump our stats into. This would make arbitrary reports much easier than loading raw YAML files and trying to make sense of them, ha! Also, this means somebody can do the smoking and send the SQLite db to another person to generate the graphs, cool!
- Kqueue loop support
As I don't have access to a *BSD box, I cannot really test this. Furthermore, it isn't clear on how I can force/unload this module from POE...
- Wx loop support
I have Wx installed, but it doesn't work. Obviously I don't know how to use Wx ;)
If you have experience, please drop me a line on how to do the "right" thing to get Wx loaded under POE. Here's the error:
Can't call method "MainLoop" on an undefined value at /usr/local/share/perl/5.8.8/POE/Loop/Wx.pm line 91.
BIG THANKS goes to Rocco Caputo <email@example.com> for the first benchmarks!
Copyright 2008 by Apocalypse
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.