The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.
By soymi on
Drupal is as much more powerful, efficient, and serious than Joomla 1.5 as Joomla is to Spip.
I know that on-file cache system disturbs orthodoxy of most square minded php real geniuses but I never said that spip cache mecanism is perfect... it is simply excellent because your site keeps working full speed in case of database crash or sql server maintenance or even during activity peaks after someone talked about your site on CNN.
Other good points are:
- Google dance will never slow down your site as much
- Maximum number of concurrent logged in users will remain the same before as far as cpu resources are concerned BUT the maximum number of normal visitors becomes AS HIGH AS POSSIBLE (as high as your Apache server can serve!).
So I have been praying every God of every religion every morning to understand why "drupalians" do not seem to take into serious consideration this on-file caching mechanism as a core optionally activated feature (would be impossibly buggy if added as a module I guess but am I wrong ?).
Any God I didn't pray ?
Comments
In general, praying has no effect
In general, praying has no effect.
Several modules implement file cache, you might want to give them a try. What needs to be done to get such a function into core:
1. Buy-in needs a compelling story + benchmarks
2. Implementation
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
evident interest for on-file cache...
No module I know of does on-file caching and still it should be core for maximum speed !...
That's an awful feature which should become core on drupal if drupal wants to remain the best CMS of all (Joomla does not need this feature because Joomla is mostly used by private individuals who care less about their visitors)
The first thing website developers are afraid of when considering to choose a CMS like Drupal or Joomla instead of home made pages is sql speed and concurrent sql accesses due to hosting limitations.
I tested Joomla cache speed which is still very slow depending on data stored on database !
Why use the database ???
This sounds like a counter productive and useless "cpu expensive" access to the database.
boost
http://drupal.org/project/boost
"still it should be core for maximum speed"
The idea was to remove PHP from the process, was it not?
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
Much more than that.
Much more than that Heine.
Compare Joomla or Drupal or any cms speed with the speed of sites made of pages ready to be served without any server side processing (no php/asp at all, no sql database queries at all).
Light speed on one hand, and delay on the other.
People do not accept ANY delay today otherwise many drop away -> php processing must be used only when no way round!
GOOGLE downgrades slow sites ranking because they know people do not want ANY DELAY (the younger the more irritated by delays).
Every page served to the public should and MUST be as fast as possible.
Thank you for reanimating,
Thank you for reanimating, though I cannot not make much sense of your comment.
In response to the "no module I know statement", I thought you might want to look at the boost module:
In addition: when PHP is completely bypassed, I cannot see how it matters in terms of speed whether on-file caching is supplied by a contributed module or something in core.
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
What would be great would be
What would be great would be to understand that is must be made "core" speedwise and bugwise because all other modules could then rely on it efficiently!
...
The search for the Sain' Drupaal continues.