I installed SS on my hosted web service, after all, if it wouldn't install there, there would be no point in playing around with it. No problems really - it's a LAMP service.

Locally, I had some problems installing - all due to the hideous swamp of software and versions I have on my own (Windows) machine. Eventually (... it included actually changing one of the install scripts!) it worked!

Anyone else think SS is slow? It's slow to come up on my hosted web service, and its slow to appear on my local machine. What's the feeling here? Does everyone think it could be a little faster, or have I just pointed at the elephant in the room?

No responses .. guessing that no one can see the elephant :D

Anyway, I agree with you, SS seems to be quite slow under certain circumstances. Without any knowledge on how SS is actually doing its caching, I think that is the biggest problem.

I have a website with only 2-3 visits a day - and every time I visit the website, it takes quite some time to present the front page. But if I reload the page is displayed nearly instantly. I am guessing that the cache is time based and after, lets say, 15 minutes in the cache the front page is "forced" to reload - so the next visit will take some time.

But please remember, I am guessing here - maybe some developers can share some info on whats actually happening :)

My conclusion: If the page is cached, its blazingly fast - if it's not, it takes too long to view.

ManifestBuilder.php:
static function staleManifest() {
return !file_exists(MANIFEST_FILE)
|| (filemtime(MANIFEST_FILE) < $lastEdited)
|| (filemtime(MANIFEST_FILE) < time() - 3600)
|| $_GET['buildmanifest'] || $_GET['flush'];
}

Yeah on some servers, the manifest-rebuild is too frequently executed.
Change the function to read:

static function staleManifest() {
return !file_exists(MANIFEST_FILE)
|| $_GET['buildmanifest'] || $_GET['flush'];
}