Hey everyone, I've been pondering the idea of working up some "official" benchmarks for RIFE and I wanted to get everyone's input. Basically, how should the test be designed. I think the data would be helpful to determine any hotspots in RIFE and pinpoint RIFE's strengths / weakness, and scalability.
1) What does everyone consider an average page on RIFE (database access, template generation, CMF access, etc.) Obviously, template generation is important, but I'm iffy on the Database access. The only way RIFE really "changes" normal DB access is it's SQL generation, but I guess that could be a hotspot and that is definitely something most of us use, so maybe it should be included. 2) How complex should the test be? (related to #1) Should we include Bean Marshaling? (aka. Form Post-back?), page redirection, database access, etc. 3) Should there be multiple "average" pages? Do we make a simple template generation page, a database access page, a bean marshaling page, an everything page, etc.? 4) What should we use to stress test the framework? Siege, something else, something custom. Personally, I think using an industry standard like Siege is probably the best idea. Cheers, Tyler _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
