afterburn
14th of September 2007 (Fri), 16:37
I love EE. I really do. I have over 3000 pictures in a few dozen galleries and performance is great. But what really pisses me off is the whole upload process. It's not bad, but it is totally annoying to me. Let me explain.
If I run EE on my hoster, I can't add pictures cause if I start the upload process, a few second and a few pictures later I get shut down due to excessive CPU usage. Understandable, as I am not the only user, but annoying.
Running EE from home is not an option, as the bandwidth etc is way too much.
Fortunately, there is a seperation within EE between where the code resides and where the images reside. So now I have an old laptop running EE, while the images are hosted at my hoster. html doesn't cost much bandwidth and the pictures can be served quick. Perfect right?
Well, no.
First of all, this is an old little computer I have to spare so it is not that quick. Uploading a batch of a few hundred pictures takes like forever to complete.
Second, I dont like being forced to run a noisy little computer 24/7 even when I am away on vacation or on work assignments from my home just so people can see my pictures.
I have this kick-ass workstation I do all my work on; 4gigs of memory and a nice quad core cpu. Why can I not use that power to resize and upload the files into an EE installation at my hoster? That would make life so much easier. Everything can be at my hoster, so I don't need to leave computers running if it is not needed, and everything can be done quick without my hoster getting their pants in a twist over any load I may cause.
There used to be talk about a program to do just this, but afaik it remained talk and even that is more than a year ago.
Any suggestions and/or solutions?
If I run EE on my hoster, I can't add pictures cause if I start the upload process, a few second and a few pictures later I get shut down due to excessive CPU usage. Understandable, as I am not the only user, but annoying.
Running EE from home is not an option, as the bandwidth etc is way too much.
Fortunately, there is a seperation within EE between where the code resides and where the images reside. So now I have an old laptop running EE, while the images are hosted at my hoster. html doesn't cost much bandwidth and the pictures can be served quick. Perfect right?
Well, no.
First of all, this is an old little computer I have to spare so it is not that quick. Uploading a batch of a few hundred pictures takes like forever to complete.
Second, I dont like being forced to run a noisy little computer 24/7 even when I am away on vacation or on work assignments from my home just so people can see my pictures.
I have this kick-ass workstation I do all my work on; 4gigs of memory and a nice quad core cpu. Why can I not use that power to resize and upload the files into an EE installation at my hoster? That would make life so much easier. Everything can be at my hoster, so I don't need to leave computers running if it is not needed, and everything can be done quick without my hoster getting their pants in a twist over any load I may cause.
There used to be talk about a program to do just this, but afaik it remained talk and even that is more than a year ago.
Any suggestions and/or solutions?