Spoti.tv is looking to hire a full time developer to make Piwik scalable!
We have great news for the Piwik community: Spoti.tv, an innovative video marketing company, is looking to hire a full time developer to help make Piwik scalable.
These last few months we have seen huge interest in Piwik and its innovative features (API, plugins architecture, dashboard), and the next step is to make Piwik function on medium to large traffic websites.
Do you want to work on an interesting project involving problem solving of a highly technical manner?
Do you want your work to be used by thousands of people?
Extract: “Piwik aims to be an open source alternative to Google Analytics. We are passionate about providing a great service to our users and are looking to hire a PHP5 expert to support our growth!”
For further details, please read the full job description on spoti.tv
This entry was posted on Wednesday, May 21st, 2008 ; category Development, Meta ; RSS comments.
May 22nd, 2008 at 7:11 pm
I am interested in participate with your project, maybe translating the documents or websites,manuals or any document, to spanish.
soo tellme if you are interested in my offer.
Best Regards
May 22nd, 2008 at 7:26 pm
Joedlovanovic, thanks for your proposition, I transmitted to the translator coordinator.
But this offer is for a real full time job as a developer :)
May 30th, 2008 at 2:54 pm
Good to hear that there are plans for making Piwik scalable. Because this will be of mayor importance to grow the number of users in the future. It has to work fine with medium and high traffic, too.
I was wondering of there are plans to show clickpaths too? For me and my projects it would be very important were specific users have been (not connected with personal data). Google Analytics doesn’t have them, but they do not give access to the raw data anyway. Reinvigorate (http://www.reinvigorate.net/) for example to offer them, and I think it would be an additional value.
June 24th, 2008 at 9:18 pm
I don’t think it requires a full time programmer to make piwik “scalable”.
There are a couple really easy things to do to make the execution faster by 50%
* Don’t use include_paths nor relative includes
* Don’t use smarty
* Don’t use ZF style self-initializing functions (see LogStatus_Config::getInstance)
I cut my execution time in half just by doing the first step. Not sure how much “faster” someone would want this to be.
June 25th, 2008 at 9:58 am
Mark, scalable mostly means being able to handle growing numbers (+millions) of visitors, the main bottleneck being the database. For example smarty would never be a problem as it is only used for viewing the reports. In the script that logs the stats (the one that needs to be really fast), we don’t use Zend.
June 25th, 2008 at 4:54 pm
Supporting a million visitors per month , per day, per second , whatever is more about setting up the servers and hardware and tweaking installation settings than optimizing a PHP script which does 3 database calls or whatever.
I sure hope that piwik is so poorly engineered that it cannot support 1 million visitors with the proper hosting and hardware configured for it. I hope that’s not what the point of this job position is.
To the bigger picture, the choice to use smarty and ZF point to a culture of un-optimized, wasteful development practices. Unless spoti.tv actually owns and is the current maintainer of piwik they won’t be able to optimize it to their needs w/o forking it. The original job post did not say whether the entire app had to be scalable or just the stat collection portion. I can see that smarty and ZF are not used during the stats logging, but I pointed out a specific instance of wasteful method calls that mimic the ZF style of getters. If a such a suggestion to reduce wasteful method call overhead is met with territorial defensiveness then I fear that spoti.tv will never achieve the robustness desired out of the box.
June 25th, 2008 at 5:50 pm
Mark, when scaling a web analytics app, scaling is about the data that comes in & processing this data. It’s not about the reporting GUI, you can use zend and smarty, it doesn’t matter..
1 million visitors is far less than what this job is about. Piwik has to scale to hundreds of millions of visitors.
The problem is really the “2 or 3″ calls to the DB which sum to billions of calls, and GB of data.
June 26th, 2008 at 8:03 am
Yeah, I first saw piwik and got all excited, but looking it over, it needs a lot of work. This is an exciting development. The db is not going to handle anything close to a large site. The future is bright for this project, but … yes it is a long long ways off.
Mark covered everything though.. not much more to say :)