4 ms·
But according to the benchmarks, cdnjs.com is worse than google and jsdelivr. http://www.cdnperf.com/#jsdelivr,google,cdnjs/http/90 http://www.cdnperf.com/#jsde
by xpose2000 13y ago
But according to the benchmarks, cdnjs.com is worse than google and jsdelivr. http://www.cdnperf.com/#jsdelivr,google,cdnjs/http/90 http://www.cdnperf.com/#jsdelivr,google,cdnjs/http/90
- jimaek 13y agoExactly, we use multiple CDNs. We are the only project to do that. This is why our performance and uptime will be always better.
- Codhisattva 13y agoBetter than Akamai? I think not.
- jimaek 13y agoAkamai does not offer a public CDN. So they are not a competitor. Apples and oranges
- Codhisattva 13y agoIf by "public" you mean free, correct. Akamai is cadillac of the CDN world so more like Apples and Organic Gourmet Apples.
- moystard 13y agoThanks for the link, we will be experimenting with cdnperf in the coming weeks, and make the move if we are happy with it.
- thomasfromcdnjs 13y agoJust be careful with those benchmarks, cdnperf is run by jsdelivr. An uptime and speed monitor based in one location is a pretty flawed way of analysing the performance of a cdn. As for Jimaeks comment above "multiple cdns" do not enforce better performance either.
- spyder 13y agoI guess they are using Pingdom which has more than 50 locations for testing, but yes it would be nice to see per-location data.
- jimaek 13y agoThis is correct. cdnperf uses multiple locations provided by pingomd and also makes sure all CDNs are tested from the exact same locations. If you have any suggestions you can submit an issue over here https://github.com/bebraw/cdnperf https://github.com/bebraw/cdnperf