Skip to main content
October 10, 2009
Question

Server very slow!!!

  • October 10, 2009
  • 1 reply
  • 1218 views

I have a windows 2003 running with ColdFusion 8, Just updated to the latest hot fix today and JRE 6.0.15

Here is a description of the problem.
The website is running very fast, and when I look at the performance on windows it only uses 1% of the processor and memory...(We get about 2,000 hits per day on the website). I noticed that after a couple of day (2 or 3).

The server is very, very slow... when I look at the performance it show that it's  using 98% of processing, at the same time when I look at the database server I see that all the MySQL connections are there and they do not disconnect... so if I restart the CF8 services, and clear all the connection the website goes back to normal.

I do NOT have the Maintain Connections checked on the data sources, so they should disconnect.

What could i do so this doesn;t happen in the server? Should I update the CF8 server? maybe cluster, or move the DB to MS SQL?

Thanks for the help..

About the machine... it's a dell with 2 xeon 3.0GHz with 4GB of memory and about 1TB Harddrive

    This topic has been closed for replies.

    1 reply

    Inspiring
    October 19, 2009

    I'd get something like FusionReactor - or even just the built-in diagnostics in CF8 I guess (never used 'em) - and have a look if any threads are hanging, or if there's any weird JDBC activity.

    2000 hits per day is a pretty quiet site, so all your kit (H/W & S/W) should handle it just fine, and definitely no need to cluster anything (well: not for traffic considerations, anyhow... fault tolerance is another thing).  With 2000 hits a minute you might want to look @ that sort of thing, but not 2000 hits a day.

    Is there anything interesting in your CF or JRun logs?

    Have you got a request timeout set in CFAdmin?

    How much RAM are you allocating to your JVM?  How many simultaneous template requests & JRun threads have you got set?  Got any possibly runaway scheduled tasks running, or anything like that?

    It might be an idea to use your onRequestStart & onRequestEnd handlers to the start and finish time of each request, to give you an easy way of spotting any requests that never finish, or any that take longer than a few seconds.  Once threads start getting chewed up by slow requests, it doesn't take mjuch for that to snowball into a non-responsive server.

    --

    Adam

    October 19, 2009

    Adam,

    I just downloaded the FusionReactor to see if that help me figure out the problem.

    I noticed that the problem is with the database connections, for some reason sometimes the connections are not disconnecting from the DB server.

    I look at the logs and I don't see anything wrong with it.

    I do have Request Time on the cfadmin set to 360s

    About the RAM from the JVM I have it set like this:

    Minimum JVM Heap Size (MB)    is blank

    Maximum JVM Heap Size (MB) is 512.

    Here is the configuration for the CF8 Server. IF you need any other information let me know.   Could it be the latest version of MySQL?

    General Settings
    Timeout requestsYes 
    Enable Per App SettingsYes 
    Request Time Limit360 seconds
    Use UUID for CFTokenNo 
    Enable Whitespace ManagementYes 
    Disable Service FactoryNo 
    Protect serialized JSONNo 
    Protect Serialized JSON Prefix// 
    Missing Template Handler
    Site-wide Error Handler
    Enable HTTP status codesYes 
    Enable Global Script ProtectionYes 
    Default CFForm ScriptSrc Directory/CFIDE/scripts/ 
    Maximum size of post data500 MB
    Request Throttle Threshold2 MB
    Request Throttle Memory200 MB
    Request Tuning
    Simultaneous request limit50 
    CFThread Pool Size10 
    Maximum number of report threads
    Maximum number of running JRun threads50 
    Maximum number of queued JRun threads1000 
    Caching
    Template cache size1024 templates
    Enable trusted cacheNo 
    Cached query limit100
    Save Class FilesYes 
    Cache web server pathsNo
    Client Variable Settings
    Default client variable storeCookie 
    Purge Interval1 hours 7 minutes 
    Client Stores
    Cookie 
    TypeCOOKIE 
    DescriptionClient based text file. 
    Purge data after time limitYes 
    Time limit10 days
    Disable global updatesNo 
    Registry 
    TypeREGISTRY 
    DescriptionSystem registry. 
    Purge data after time limitYes 
    Time limit90 days
    Disable global updatesNo 
    Memory Variables
    J2EE SessionsNo 
    Application Variables
    Enable Application VariablesYes 
    Default Timeout2,0,0,0 
    Maximum Timeout2,0,0,0 
    Session Variables
    Enable session variablesYes 
    Default Timeout0,0,20,0 
    Maximum Timeout2,0,0,0