Any overhead with Url Aliases when caching?

I have the page cache activated on my Drupal installations. I have avoided using URL Aliases on my new website, as I expect the node count and visitor numbers to be high over the coming year.

Am I right in thinking that performance will be better without URL Aliases, even when caching is activated? I understand that the page cache is for anonymous visitors only.

Thanks, Darren

200.000 nodes (images) per annum Drupal implementation?

Can Drupal handle 200.000 nodes per year? Each node to have one or two images either via image module (attached images) or CCK imagefield (any other suggestions?). What hardware will be needed to serve this volume to around 150 users? Can Apache and MySQL handle this volume efficiently?

Thanks in advance for your help.

Remove redundant indexes. Performance benefit?

Please have a look at the issue I created:
http://drupal.org/node/172724

Thanks, Joep

Merging javascript?

In http://drupal.org/node/173957 I asked about why the .js and .css files are being re-requested on every pageview. I still haven't worked out why this is happening. However while researching I turned up something interesting.

Why do .js and .css files reload on every pageview?

I'm looking at improving the page load time on my site. Firebug says my /tracker page takes 2.9 seconds to load in the browser, which is a bit excessive. I did some research on acceptable page load times, and found there's quite a range of opinion on what's ok.

I have been browsing the performance hints in the drupal handbook ... but they don't cover one thing I'm seeing.

Pages

Subscribe with RSS Subscribe to RSS - Deprecated - Performance and scalability