Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: slowness...

  1. #1
    Join Date
    Mar 2009
    Posts
    137

    Default slowness...

    does anyone have any ideas about this?
    I have a link2 and aparently vpslink are telling me its out of resources which is why is going slow at the moment but

    Real memory: 128.17 MB total / 76.02 MB free Swap space: 255.99 MB total / 242.79 MB free

    its got 76mb of mem free and its using 4% cpu usage at most... and ive got about 2.5gb free space...so does anyone else know where i can look? as as far as i can tell its resources are fine..

  2. #2
    Join Date
    Jun 2008
    Posts
    232

    Default

    I would ask the tech that's handling your ticket to identify which resource it is.

    (Guessing) Inodes maybe?
    Code:
    df -i

  3. #3
    Join Date
    Mar 2009
    Posts
    137

    Default

    they basically told me that wasnt their problem...

    localhost:~# df -i
    Filesystem Inodes IUsed IFree IUse% Mounted on
    /dev/sda1 622592 48546 574046 8% /
    tmpfs 16406 2 16404 1% /lib/init/rw
    udev 16406 296 16110 2% /dev
    tmpfs 16406 1 16405 1% /dev/shm
    none 16406 1 16405 1% /dev/shm

    thats what df -i says? looks ok but im not sure?

  4. #4
    Join Date
    Jun 2008
    Posts
    232

    Default

    Quote Originally Posted by askewdread View Post
    they basically told me that wasnt their problem...
    That is unfortunate, since if someone has investigated a problem to the point where they have identified the cause, it's not usually that much more effort to reveal it. Proceeding to fix it is another matter though.

    Quote Originally Posted by askewdread View Post
    localhost:~# df -i
    Filesystem Inodes IUsed IFree IUse% Mounted on
    /dev/sda1 622592 48546 574046 8% /
    [snip]

    thats what df -i says? looks ok but im not sure?
    Looks fine. What it means is:
    Total Inodes: 622592
    Used Inodes: 48546
    Free Inodes: 574046

    You can read up a bit more on inodes at wikipedia.

    In summary as to why it could have applied here:
    If you have lots of small files in your filesystem, then it's possible to end up with free space available, but no inodes. In your case, you have free space and free inodes, so that's not the likely cause of your particular problem.

    If the problem goes away, I'd drop it, but if it persists, try re-opening the ticket and requesting clarification on exactly which resource is being referred to so that you can investigate it further.

  5. #5
    Join Date
    Mar 2009
    Posts
    137

    Default

    Quote Originally Posted by chriss View Post
    That is unfortunate, since if someone has investigated a problem to the point where they have identified the cause, it's not usually that much more effort to reveal it. Proceeding to fix it is another matter though.



    Looks fine. What it means is:
    Total Inodes: 622592
    Used Inodes: 48546
    Free Inodes: 574046

    You can read up a bit more on inodes at wikipedia.

    In summary as to why it could have applied here:
    If you have lots of small files in your filesystem, then it's possible to end up with free space available, but no inodes. In your case, you have free space and free inodes, so that's not the likely cause of your particular problem.

    If the problem goes away, I'd drop it, but if it persists, try re-opening the ticket and requesting clarification on exactly which resource is being referred to so that you can investigate it further.
    thanks for that, this is my db server only so it should never really change as the data is always the same and the servers never touched.. but it seems to be running a bit better now so will see how it goes


    Thanks

  6. #6
    Join Date
    Jul 2009
    Location
    New York
    Posts
    464

    Default

    if it's a database than it's probably misconfigured. If settings too low than there will be too much swapping. Though it's hard to guess when none of us knows what's in your database and what exactly you are running.
    Last edited by Cwewmpz; 10-27-2009 at 02:41 PM.
    Happily on a Link3. Feel free to request a refferal code that takes a 10% lifetime discount off your hosting.
    Please open a SUPPORT TICKET AND CALL vpslink to resolve your vpslink problems FIRST
    I am a CUSTOMER Only. Any vpslink issues should be directed to Matt@VPSLink and/or Michael@VPSLink

  7. #7
    Join Date
    Mar 2009
    Posts
    137

    Default

    it runs 2 300mb mysql db's that a program constantly uses
    the mysql server doesnt use much memory but that could make sense if its doing to much swapping...i set it up using the low memory suggestions on the wiki but do you know what i can check?

  8. #8
    Join Date
    Mar 2009
    Posts
    137

    Default

    sigh and now its taking an hour to start programs that rely on the database again, does anyone have any idea where i can look? the only other time this happened it was someone on the physical host im on that was tieing it all up but they have already told me its not their problem this time and nothings been changed seince then...

  9. #9
    Join Date
    Mar 2009
    Posts
    137

    Default

    this is before the programs start
    Code:
    localhost:~# free
                 total       used       free     shared    buffers     cached
    Mem:        131248     107420      23828          0       4456      71396
    -/+ buffers/cache:      31568      99680
    Swap:       262136          0     262136
    this is when they try to start... the only differnce i see is its caching alot more?
    Code:
    localhost:~# free
                 total       used       free     shared    buffers     cached
    Mem:        131248     129136       2112          0        480      94984
    -/+ buffers/cache:      33672      97576
    Swap:       262136         20     262116

  10. #10
    Join Date
    Mar 2009
    Posts
    137

    Default

    Code:
    At this time, I see several remote connections to your MySQLd service
    port (3306):
    
    root@localhost:/dev# netstat -an|grep 3306
    tcp        0      0 0.0.0.0:3306            0.0.0.0:*
    LISTEN
    tcp        0      0 209.40.201.130:3306     67.223.238.172:36114
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.228.73:45549
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:45474
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:36115
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:37923
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:45475
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:36112
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:37920
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:45472
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:36113
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:37921
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:45473
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:36116
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     209.40.201.130:42102
    TIME_WAIT
    tcp        0      0 209.40.201.130:3306     67.223.238.172:37918
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:36110
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:45470
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:37919
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:36111
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:45471
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:45468
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:37917
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:36109
    ESTABLISHED
    tcp        0      0 209.40.201.130:3306     67.223.238.172:45469
    ESTABLISHED
    
    Note that even though MySQLd may not be using much CPU, each query uses
    disk I/O, which can cause slowness in other services.
    This is what vpslink are telling me...as i said to them this usually has twice this amount as i only have 1 server trying to start at the moment... so theres usually twice this amount and it still runs ok...but now with even just 1 its killing it and nothings been touched on this server for at least 2 months..... so to me it seems something on their end...but they say its not :s

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •