5.0.4 performance release
March 22nd, 2007 by Richie
I have been thinking of the phases post the 5.0.3 release. I am getting the feeling that since 5.0.3 is so much geared toward deployment, we will soon have to face performance issues. So it makes sense to address those in the 5.0.4 release.
5.0.4 will focus on improving the performance of the product. It will be a good icing on top of the 5.0.3 stability release. This will also ensure that the people who are using vtiger get a good user experience.
Adding features is not an issue at all. Ensuring that they work the way they work and a little more is where we have the issues ;-). Things always work 80% well. The rest 20% is the killing part!
Paretos 80/20 rule seems to be all pervasive.
What do you guys feel?




Have there been any benchmarks run on vtiger? At what point will there be any performace loss?
Have you used it with APC or php accelerator?
Would caching help at all?
Hmm not sure it would thinking about it.
Well, we did not run any perf benchmarks of late. I did test vtiger with APC and a few other tools and the performance had increased considerably.
I was not sure of the impact on the product when I had run the product and hence did not start bundling it with vtiger.
But I am sure, there will be significant gains with these tools.
Hi Richie,
I totally agree with you, after stabilization, a performance release is needed to completely put the whole community back on rails.
Want to add as well that I have been critical on the road map coming from vTiger team, but this post gives the feeling that we are all on a good path.
What about security? are you going to review this field during the stabilization phase or will it be a proper version as well?
Keep up the good work guys,
Bye
I am not sure I understand the Security part Krem. Kindly elaborate.
vtiger is a community product and all of you have the right to state your opinion. All of us need not agree on the same thing. The idea is that all of us have the liberty to speak up and be heard. So feel free Krem.
5.0.3 is a stability release
5.0.4 will be a performance release
Security is just another field to take care of in a software, when I look at other projects like drupal, I see security mailing list which regularly release new patches…
That’s why I am thinking that a security focused release could be a good idea after stability and performance to just verify how secured vTiger is actually.
A usability release could be useful as well, focused on the user experience and conclusions.
Doing those tasks one by one allow to define very precisely steps and procedures that we will be able to use in future versions.
Even in the wiki a “release validation” part could be very useful with different categories like “stability, usability, performances, security, etc.”. Each of those categories could contain tutorials on how to test a release, links to useful softwares, etc.
Tell me if you need more clarifications.
Byebye
Well, I am not sure if we will have a point release for the Security. I do not have that in mind as of now.
In fact, whenever we are made aware of any vulnerability, we fix it asap and have it rolled out with the product.
But yes, some point down the line, if there be anything that comes up which is mega, we will certainly consider coming out with a point release to address the same.