TehUpload API

[Source]

I think its about time youmeo got their main server sorted? At least get the SQL optimised or moved to another server, as thats what is causing the issues (from my past experience, again this is not a dig at youmeo as they always think it is). Your CPU usage must be at a good 200-400% (depending on processor) during peak times, you need to spend a bit more time getting a better server setup.

Anyway, thats not my opinion, not to better youmeo in anyway. Just my 2cents.

edit// Also things such as moving SSH off of the default ports to stop brute forces easily finding it, same with FTP. I would also recommend making the FTP IP authorised as that is a great way of stopping attacks against those sort of services.

[Dentafrice]

Actually, we have to upload a large amount of images every day as with a social networking site you don't just upload one image, you have to upload several versions of a single image in different formats/different sizes etc.

There is no way TU would be able to handle all of ymo's images.

Of course it couldn't :rolleyes:

Ever since you and Greg said that this morning, me and a few friends have been "running tests" on the TehUpload server.

Now I know for a fact that Youmeo cannot upload more then 20 images per minute, it's not that popular.

So we've accounted for 20*4 = 80, with 4 being a reasonable amount for 4 image sizes, as there is no need for different image types.

So right now we have a few users running scripts that is uploading over 100-150 images per minute (what we can reasonable say from our statistics in the past few minutes).

So far, in the past 4 minutes, our server has been able to correctly parse, upload/store, and provide feeds for over 3,500 images.. and our server hasn't flenched a bit.

I'm 95% sure TehUpload's servers could handle "Youmeo's images", considering it can't be that many.. and it can't match up to the tests we have been putting it through.

Like Jewish Bear's "dongs" images back in July/August.. hundreds and thousands of them were handled by TehUpload, and uploaded and stored.. without our server going down once.

So please, quit trying to make Youmeo look bigger then it is, we know it's pretty big.. but not as big as you make it seem with your "blabla can't handle ymo's images".

[Invent]

Now I know for a fact that Youmeo cannot upload more then 20 images per minute, it's not that popular.

How can you know that for a fact? You have no data of how popular Youmeo is and how active it's user base is. If it wasn't that popular we wouldn't have made it through to Round 1 of the Open web awards.

Also Caleb, what I'm saying is, you couldn't handle ALL of ymo's images. We have over 250,000 images and you couldn't handle them all in *7 different formats. If we were to use t.u it would have to support all our images, not just the new ones.

[Source]

Who says he doesnt have other resources up his sleeve?

[Fehm]

I reckon its great =]

Ty for this tbh

[Invent]

He may do, but not more than what we have up our sleeves and what we can get.

[Dentafrice]

He may do, but not more than what we have up our sleeves and what we can get.

If you have that many resources up your sleeve, I'd love to know why Youmeo is still on a ****** server?

I would think that you would care more about the status of your site, and the speed and avaliability of the site (the uptime is awful), then which image hosting provider you use..

[Awfy]

If you have that many resources up your sleeve, I'd love to know why Youmeo is still on a ****** server?

I would think that you would care more about the status of your site, and the speed and avaliability of the site (the uptime is awful), then which image hosting provider you use..

Caleb, your site doesn't even match what is needed for Youmeo. For a matter of fact we all sat down as a team last night until 9pm going through every file to try and optimize the site. You wouldn't be able to do it if you tried as you don't have the patient or know how. Just because you are able to out-smart a forum doesn't mean your site's going to recieve awards or even get the chance to. Industry experts and management see Youmeo for what it's worth and they'll all jumping on board. Wait till TehUpload has the media coverage we do then see how well your server does

[Invent]

If you have that many resources up your sleeve, I'd love to know why Youmeo is still on a ****** server?

I would think that you would care more about the status of your site, and the speed and avaliability of the site (the uptime is awful), then which image hosting provider you use..

Who says it's the server? The server(s) are fine. One of the reasons why it's a bit slower than it should be is performance/efficiency issues from bits of old code which we're currently re-coding.

Oh and the uptime isn't awful, the server hardly ever fails or needs rebooting/etc.

TehUpload apparently currently stores 16,906 images

Youmeo has 253,302 image urls in it's database, times that by 4 for the amount of sizes we currently offer: 1,013,208 images. Not to forget the fact we're going to be providing a futhur 5 new image sizes..

What we're saying is, you couldn't handle our images with the servers you have now.

[Source]

Guys, guys, no need to get nasty about it.

//edit - just a suggestion.... but why store that amount of images in different sizes when you could setup an imaging server (on the cheap) and have it resize on-the-fly and memcache it... Although that does have alot of flaws.