FUDforum
Fast Uncompromising Discussions. FUDforum will get your users talking.
Home » Imported messages » comp.lang.php » Re: Windows binaries 64bit for PHP
Show: Today's Messages :: Polls :: Message Navigator
Return to the default flat view Create a new topic Submit Reply
Re: Windows binaries 64bit for PHP [message #178022 is a reply to message #178020] Thu, 10 May 2012 19:12 Go to previous messageGo to previous message
Jerry Stuckle is currently offline  Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
Senior Member
On 5/10/2012 3:01 PM, Michael Fesser wrote:
> .oO(Jerry Stuckle)
>
>> On 5/10/2012 2:50 AM, Michael Fesser wrote:
>>> .oO(Jerry Stuckle)
>>>
>>>> On 5/9/2012 6:23 PM, Michael Fesser wrote:
>>>> > .oO(Jerry Stuckle)
>>>> >
>>>> >> OK, so you do it "on the fly" and store the result. That still takes
>>>> >> more time than doing it once and forgetting it. Your way, you have to
>>>> >> check on every request for the image to see if your size exists before
>>>> >> deciding if you need to rescale it or not. Another unnecessary waste of
>>>> >> processing time.
>>>> >
>>>> > You can catch that with Apache's error handling. If the image is not
>>>> > found, the 404 error handler kicks in and creates it.
>>>> >
>>>> > Micha
>>>> >
>>>>
>>>> Which is even more overhead...
>>>
>>> Wrong. The little overhead happens just once if the image doesn't exist
>>> yet. After then it's just a static resource, which will be delivered
>>> directly by the server.
>>
>> Have you actually checked how much overhead there is to process a not
>> found? It is quite significant.
>
> Even if - how often does it happen? Exactly once for every image. So
> where's the problem?
>
> In many other cases the first request causes a lot of overhead as well,
> be it the initial compiling of a PHP script or the downloading of a
> static resource to the client. The first request always takes the most
> time. After then the data is taken from some kind of cache. And here
> it's exactly the same - on the first request the image is created, after
> then it's a normal static resource. In practice there's absolutely no
> problem with that and no wasted CPU time.
>
> Micha
>

And when you create the images one time, it's done ZERO times.

And no, the data isn't always taken from some kind of cache. It depends
on a lot of things. For instance, a PHP script is compiled every time
it's called unless the server can determine nothing has changed
(generally not the case) or you have installed additional PHP caching
software. Web servers do not cache compiled code, and neither does the
PHP module by itself.

Back to the subject at hand - every time the system has to handle a 404
there is wasted time. And it is a relatively significant amount of
time. Adding the necessity of resizing an image to that can be costly
on a busy server.

Of course, if all you get are 200 hits/day, it doesn't make any
difference how you code your scripts.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: variable replacement in string
Next Topic: Re: Windows binaries 64bit for PHP
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Nov 28 13:43:10 GMT 2024

Total time taken to generate the page: 0.03646 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.1.3.
Copyright ©2001-2023 FUDforum Bulletin Board Software