in reply to Re^3: Timing concerns on PerlEX/Mod_Perl
in thread Timing concerns on PerlEX/Mod_Perl

I isolating is kind of hard since I use one central code that loads functions. So it would pretty much means rewriting the entire code.

What PerlEX and Mod_Perl do is they pre-load a lot of the variables and start up into memory and then execute threads that access the persistent data.

personally I do not think im storing that much data into ram that would give it issues in spawning threads but it could be my use of namespaces :/..if there was only a way..maybe ISAPI component to monitor script start up or etc :/...or maybe some apache functions?
  • Comment on Re^4: Timing concerns on PerlEX/Mod_Perl

Replies are listed 'Best First'.
Re^5: Timing concerns on PerlEX/Mod_Perl
by BrowserUk (Patriarch) on Jul 26, 2008 at 06:25 UTC

    You don't have rewrite or even change the script.

    Make a copy of it, with the timing code, under a different url.

    Comment out everything except the timing code and run it.

    Still the same effect?

    1. Yes: Your server set-up isn't what you think it is or it is screwed.
    2. No.
      1. Uncomment half the script.
      2. Run it again. Still okay?
        1. Yes: Uncomment half of the remaining code. Goto 2b
        2. No: Re-comment half the code you just uncommented. Goto 2b

    You'll rapidly find the line of the code that screwing you.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
      Well if I run the script with 2-3 people using it. It runs hassle free. The issue happens when I make it live.(but CPU usage doesn't go up)

      I can try though..but since the code is written in a centralized environment. It is more dynamic, example:

      I write in html: <*Get List|type:all*>

      so only thing I can really comment out are the objects. Rest is kidna dependent. For a better understanding here is my code structure:

      I have 4 name spaces:

      main - the main namespace which calls the other namespaces and handles outputting of data from common(headers) and frame(html).

      common - stores all the basic stuff like opening files, accessing database and etc. it also loads query strings and headers.

      frame - loads the html, the advanced functions like login account and etc which is made up of calling the common. After loading HTML it loads the Skin namespace on the loaded html.

      Skin - loads the layout, all the images, textboxes, forms, assigns ids and other more advanced objects.



      Sigh..my urge to have a centralized structure is probably my biggest downfall..its good and convenient, but if the core has issues, makes it much harder to debug :(
[reply]

        Well if I run the script with 2-3 people using it. It runs hassle free. The issue happens when I make it live.(but CPU usage doesn't go up)

        Have you tried loading your site up from 3 clients to whatever your production load is? If your server is only set to handle a certain number of requests at a time, your other requests may be waiting behind those that are currently processing. These waiting requests would not necessarily cause the load of the machine to increase.

        Try bringing up the number of clients slowly and see when the problem starts. Then tune your web server / web farm to handle the required number of connections.

        --MidLifeXis

[reply]
        my urge to have a centralized structure is probably my biggest downfall

        It seems to me that you know what your problem is, but just don't want to admit it (to yourself) :)

        Vis.

        I have 4 name spaces: main - the main namespace which calls the other namespaces and handles outputting of data from common(headers) and frame(html). common - stores all the basic stuff like opening files, accessing database and etc. it also loads query strings and headers. frame - loads the html, the advanced functions like login account and etc which is made up of calling the common. After loading HTML it loads the Skin namespace on the loaded html. Skin - loads the layout, all the images, textboxes, forms, assigns ids and other more advanced objects.

        You're replicating everything, for every request. And hoping that mod_perl/perlez will take care of things. I think you are expecting far too much of them.

        When I said earlier that I know nowt about them, I meant that I know nothing about tuning them. I do know what they do, but have never had the desire to use them. They seem altogether too hackish to me.

        I've no use for Apache either. For example, you said in your OP that your memory consumption is approaching 1.7GB. In that same space I can install 3500 concurrent copies of TinyWeb, each capacble of servicing dozens of concurrent requests.

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom