Pielāgotas 404 lappušu briesmas

One customer running a single WordPress was using a 4x vCPUs instance on Amazon AWS®. Bet CPU un slodzes lietojums bija tik augsts, bez redzamiem iemesliem (apmeklētāju skaits bija samērīgs). Tomēr: katrs 404 izraisīja milzīgu CPU un joslas platuma patēriņu! Tika veikts tests un 404 was replaced by a flat and tiny 324 bytes HTML file. The result: the instance size could be divided by two, so halving all expenses (including the bandwidth).

When using a custom 404-page: one should not forget that even a simple dead link to an image will trigger an expensive and huge HTML code being returned to the browser, resulting in sluggish speeds for the visitors as well!

Citiem vārdiem sakot: do not do it, even if it looks pretty to the eyes.