For me it redirects to the new server already.

For many people it will directly work with the usual address, at least after few hours it will work.
Those who get the old site with the usual address are those who went on the site just before the change, or who have an ISP who does not refresh often the DNS cache (like mine, Edpnet)
In worse case, tomorrow evening nearly all DNS server will have been refreshed with the new server address.
I prefer that "new.imcdb.org" is not too much used, else people will post links with it in comments, which I'll have to fix when I'll drop that sub-domain...

Oh, sorry, but new.imcdb.org is the only page I can use right now. The old doesn't work any more, resp. I cannot write there, and there is no redirection, as chicomarx says.

Not for me. I see, I can write and submit movies and pictures either with www.imcdb.org or http://new.imcdb.org/ . It's like a double-deck imcdb.

The new site works fine and it's very fast!

MANY THANKS @Antp for your work!

I try to reduce this http://www.imcdb.org/vehicle.php?id=352084 960px × 498px and it's not a HD picture

If I use www.imcdb "Re-use current picture as source (for resizing)" the error message is "Warning: copy(): Unable to access http://www.imcdb.org/images/352/084.jpg in /var/www/html/imcdb/upload.php on line 185 "

If I use http://new.imcdb.org/upload.php?id=352084&movieid=55805 the message is the same Warning: copy(): Unable to access http://new.imcdb.org/images/352/084.jpg in /var/www/html/imcdb/upload.php on line 185

Seems to be a problem with the "copy" function in PHP 5.3.x (the old server used a much older PHP version)
I'll try to find why or replace the copy by something else.
In the meantime you'll have to save the picture locally and reupload it

I fixed the problem, but as my internet connection was down just before I could finish, my test page stayed on the site some time, and the copy of the Alfa picture that I used for test was identified there

Thanks, great work. It loads quick as a flash too.

Yeah, generally great work, let's hope it will be much better now... But it started to work very slow now (sorry I had to write about it ).

opps...well. I thought was only my internet connection

S-l-o-w ...

except that here I do not see what could cause that
CPU is not fully used
RAM is used at 1/4th
There aren't queries waiting and piling up like when it was becoming slow in the old server...
Maybe it is just OVH's network which is a little full
You can see at the bottom of the page the time it took to the server to generate it. Usually it is below 0.5 second. If you notice on some particular page that the time is always higher than that, you may report these pages here. But for example right now it took few seconds to load a page but it was generated in 0.008 sec: it is a network problem and not a server problem (luckily :D)
It may also sometimes be an attack made to the server, I had that last weekend: for one hour it was very slow to respond, because another server was "attacking" it

It seems that Goggle bot is following some broken link, generating tens of error 404 per second, it probably does not help...

It tooks around 10"-20" a page can be loaded.

Lots of visitors, I can't do much... I could block Googlebot, but in another way it is good that it indexes the site.

After few days it will probably be possible to optimize MySql for the database, but for that it has to have some data on what is the most used in the database... so we'll have to wait.

I have some improvements to do anyway, but I am not sure it will help much and I do not know when I'll do these

It seems to be the fault of the vehicle search when done without any restriction (i.e. list of all vehicles of the site).
It may be the Googlebot which travels through these pages.
I'll try to disable that search for the moment.

Rather slow now...

Yes, cf messages above.
But we probably found the problem: the vehicle search done without any parameter (i.e. list of ALL vehicles of the site) was very slow, and probably performed by the googlebot who is exploring all pages.
So I locked such search for the moment, and will make it properly (in a similar way as what I did for the "view all comments" which is also heavy but not slow at all)

Since no one is complaining anymore I guess that it solved the problem?