Yep, especially customer's pictures are pretty big. That's because the DB was already like this when we started the new website. Running ImageMagick's convert on all images would improve things quite a lot :) Nico Sven Van Caekenberghe writes:
On 30 Jan 2014, at 11:17, phil@highoctane.be wrote:
Hello,
I paid a visit to the site.
Looks good. Images are loading awfully slow tough.
Isn't there any image caching? It seems that they aren't resized and the web browser loads the big pictures for each little picture (it does as a matter of fact).
http://www.reflex-vacances.fr/location-vacances/appartement-le-mans/c755c60d
loads
http://www.reflex-vacances.fr/img/ebb76d6a/Photomaison037.jpg
which is quite big (1.7MB each, 3 of them on that page).
There is also a couple of js requests instead of one big load.
The whole loading on an empty cache is more than 10 seconds. Including Google Maps details, 16. Yikes, that's a hell of a slow beast.
I can't help but think about someone looking at this from a mobile device, even on 3G.
The whole network thing (looking at the Chrome Devtools Network tab) seems to avoid a couple of best practices:
https://developers.google.com/speed/docs/best-practices/rtt
like:
- https://developers.google.com/speed/docs/best-practices/rtt#CombineExternalJ...
Maybe https://developers.google.com/speed/docs/best-practices/rtt#ParallelizeDownl... could help with all of those pictures.
Some ImageMagick preprocessing would definitely help with the images.
I tell you that because we implemented such a kind of site in the past (not Pharo) and had to make it work fast (this was for expensive houses, visitors were kind of impatient).
Also, I just help businesses avoid this kind of slowdown as one of my business offerings, so I couldn't resist ;-)
I didn't look that carefully, but yes, great analysis.
Image sizes are very important for a site like that, ImageMagic is your friend, sizes should be in the 100-200-300 Kb range.
YSlow is also a very good tool.
Sven
Regards, Phil
On Thu, Jan 30, 2014 at 11:02 AM, Nicolas Petton <petton.nicolas@gmail.com> wrote:
Torsten Bergmann writes:
runs 100% in Pharo + Iliad + MongoDB.
"Look ma - no apache or nginx".
Hi!
Apache is used as a frontend server, and many images are indeed in the db, thus served through Pharo.
The Pharo image is a 1.4, the VM is Cog, with a typical Mongo+Voyage setup. Most of the DB data is cached by Voyage, which partly explains the speed.
Mongo and Pharo are running on the same machine, there's no special caching except for what Voyage provides by default.
The Iliad app is served by Kom, and we have many bash scripts to monitor, auto-restart and manage the app (we manage SmalltalkHub in a similar way).
Cheers, Nico
-- Nicolas Petton http://nicolas-petton.fr
-- Nicolas Petton http://nicolas-petton.fr