>
> The time it takes to process a request?
> The time it takes to develop?
> Are you going to implement caching?
> Are you going to try multiple datasources (of various types)?
I realize that performance is a complicated issue. I'm currently
finding out about different performance testing methods. I'm also
going to compare features of frameworks and I'm going to measure
development time and other factors while coding test application with
each of the frameworks.
I'll propably run performance tests both with and without caching.
Propably only datasource will be MySQL-database.
>
> IMO, a real-world app should have the following features:
> - User registration
> - Authentication
> - Database interaction
> - At least 5 models, which cover various types of associations
> - Data validation
> - Security
> - Session management
> - Web service API (at least provisioning)
> - Administrative interface
I'm thinking along the same lines, except I'm not sure if
administrative interface is essential when comparing performance.
-Kalle
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
No comments:
Post a Comment