Lion slow performance due to hanging TCP sessions

After upgrading to 10.7.2 I experienced that Safari and Mail hangs.
After a reboot the problem was gone but occured again after a while.
I found out that a lot of TCP sessions were in the CLOSE_WAIT state.
The affekted deamon was ocspd.
I killed the deamon and it restarted automatically. The problem related to hanging https sessions Safari an Mail was gone.
The problem occurs again and again.
Does someboda have an idea how to solve this issue.
Bellow I listed some output:
Hinkelstein:~ mav$ sudo lsof -i -P | grep CLOSE_WAIT
applepush  372           root   13u  IPv4 0xffffff801434e320      0t0    TCP 192.168.10.52:53317->nk11p01st-courier018-bz.push.apple.com:443 (CLOSE_WAIT)
WebProces 3720            mav   16u  IPv4 0xffffff802e9ce880      0t0    TCP 192.168.66.154:54481->tls_server.uslendernetwork.com:80 (CLOSE_WAIT)
WebProces 3720            mav   17u  IPv4 0xffffff80330fac20      0t0    TCP 172.20.1.73:58913->172.20.5.7:443 (CLOSE_WAIT)
PubSubAge 7794            mav   19u  IPv4 0xffffff80344426c0      0t0    TCP 172.20.1.73:59003->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root    3u  IPv4 0xffffff802f6b84e0      0t0    TCP 172.20.1.73:58847->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root    7u  IPv4 0xffffff803310d6c0      0t0    TCP 172.20.1.73:59014->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root    8u  IPv4 0xffffff802e03ba40      0t0    TCP 172.20.1.73:58849->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root    9u  IPv4 0xffffff802e952c00      0t0    TCP 172.20.1.73:58845->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   10u  IPv4 0xffffff8033150fa0      0t0    TCP 172.20.1.73:58850->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   11u  IPv4 0xffffff80330f6c00      0t0    TCP 172.20.1.73:58878->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   12u  IPv4 0xffffff8034443c20      0t0    TCP 172.20.1.73:58843->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   13u  IPv4 0xffffff802e8b0160      0t0    TCP 172.20.1.73:58844->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   14u  IPv4 0xffffff80331404e0      0t0    TCP 172.20.1.73:58856->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   15u  IPv4 0xffffff802e9b54e0      0t0    TCP 172.20.1.73:58892->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   18u  IPv4 0xffffff802e8afa40      0t0    TCP 172.20.1.73:58867->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   19u  IPv4 0xffffff802f6bafa0      0t0    TCP 172.20.1.73:58863->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   20u  IPv4 0xffffff803317dc20      0t0    TCP 172.20.1.73:58885->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   21u  IPv4 0xffffff8033164c20      0t0    TCP 172.20.1.73:58884->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   22u  IPv4 0xffffff8033141320      0t0    TCP 172.20.1.73:58871->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   23u  IPv4 0xffffff80331396c0      0t0    TCP 172.20.1.73:58874->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   24u  IPv4 0xffffff802e9b7160      0t0    TCP 172.20.1.73:58881->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   25u  IPv4 0xffffff8033171c00      0t0    TCP 172.20.1.73:58897->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   26u  IPv4 0xffffff801434f880      0t0    TCP 172.20.1.73:58918->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   27u  IPv4 0xffffff80330f7320      0t0    TCP 172.20.1.73:58877->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   28u  IPv4 0xffffff802f6c4880      0t0    TCP 172.20.1.73:58899->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   29u  IPv4 0xffffff802e8bac00      0t0    TCP 172.20.1.73:58917->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   30u  IPv4 0xffffff803316afa0      0t0    TCP 172.20.1.73:58964->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   31u  IPv4 0xffffff8034441160      0t0    TCP 172.20.1.73:58906->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   32u  IPv4 0xffffff802e956500      0t0    TCP 172.20.1.73:58985->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   33u  IPv4 0xffffff8033172a40      0t0    TCP 172.20.1.73:58905->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   34u  IPv4 0xffffff8033106c20      0t0    TCP 172.20.1.73:58935->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   35u  IPv4 0xffffff802e9b6a40      0t0    TCP 172.20.1.73:58904->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   36u  IPv4 0xffffff8033136c00      0t0    TCP 172.20.1.73:58965->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   37u  IPv4 0xffffff8033138880      0t0    TCP 172.20.1.73:58980->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   38u  IPv4 0xffffff8033147c00      0t0    TCP 172.20.1.73:58915->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   39u  IPv4 0xffffff802e954160      0t0    TCP 172.20.1.73:58966->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   40u  IPv4 0xffffff8033138fa0      0t0    TCP 172.20.1.73:58938->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   41u  IPv4 0xffffff8033149160      0t0    TCP 172.20.1.73:58933->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   42u  IPv4 0xffffff8033103a40      0t0    TCP 172.20.1.73:58939->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   43u  IPv4 0xffffff8033142880      0t0    TCP 172.20.1.73:58930->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   44u  IPv4 0xffffff80331056c0      0t0    TCP 172.20.1.73:58940->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   45u  IPv4 0xffffff8033173fa0      0t0    TCP 172.20.1.73:58937->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   46u  IPv4 0xffffff801434dc00      0t0    TCP 172.20.1.73:58941->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   47u  IPv4 0xffffff803314fa40      0t0    TCP 172.20.1.73:58992->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   48u  IPv4 0xffffff803312ffa0      0t0    TCP 172.20.1.73:58975->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   49u  IPv4 0xffffff803314b500      0t0    TCP 172.20.1.73:58981->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   50u  IPv4 0xffffff8033104880      0t0    TCP 172.20.1.73:58967->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   51u  IPv4 0xffffff80330fa500      0t0    TCP 172.20.1.73:58982->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   52u  IPv4 0xffffff802e9cf6c0      0t0    TCP 172.20.1.73:59033->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   53u  IPv4 0xffffff8033142160      0t0    TCP 172.20.1.73:58969->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   54u  IPv4 0xffffff802e9ccc00      0t0    TCP 172.20.1.73:58989->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   55u  IPv4 0xffffff8033149880      0t0    TCP 172.20.1.73:58970->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   56u  IPv4 0xffffff802e9b8de0      0t0    TCP 172.20.1.73:59004->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   57u  IPv4 0xffffff80331516c0      0t0    TCP 172.20.1.73:58971->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   58u  IPv4 0xffffff803317cde0      0t0    TCP 172.20.1.73:58972->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   59u  IPv4 0xffffff8034623500      0t0    TCP 172.20.1.73:59023->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   60u  IPv4 0xffffff802e03a4e0      0t0    TCP 172.20.1.73:59081->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   61u  IPv4 0xffffff803461fc00      0t0    TCP 172.20.1.73:59034->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   62u  IPv4 0xffffff803314a6c0      0t0    TCP 172.20.1.73:59042->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   63u  IPv4 0xffffff802e9944e0      0t0    TCP 172.20.1.73:59075->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   64u  IPv4 0xffffff802e9cda40      0t0    TCP 172.20.1.73:59016->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   65u  IPv4 0xffffff803312ea40      0t0    TCP 172.20.1.73:59026->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   66u  IPv4 0xffffff8033161a40      0t0    TCP 172.20.1.73:59036->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   67u  IPv4 0xffffff80331364e0      0t0    TCP 172.20.1.73:59018->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   68u  IPv4 0xffffff80331684e0      0t0    TCP 172.20.1.73:59056->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   69u  IPv4 0xffffff8034621fa0      0t0    TCP 172.20.1.73:59019->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   70u  IPv4 0xffffff8033173880      0t0    TCP 172.20.1.73:59020->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   71u  IPv4 0xffffff802e8b0880      0t0    TCP 172.20.1.73:59035->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   72u  IPv4 0xffffff803310cfa0      0t0    TCP 172.20.1.73:59021->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   73u  IPv4 0xffffff8033175500      0t0    TCP 172.20.1.73:59067->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   74u  IPv4 0xffffff80331794e0      0t0    TCP 172.20.1.73:59022->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   75u  IPv4 0xffffff803314e4e0      0t0    TCP 172.20.1.73:59148->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   76u  IPv4 0xffffff8033172320      0t0    TCP 172.20.1.73:59052->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   77u  IPv4 0xffffff802f6c5de0      0t0    TCP 172.20.1.73:59095->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   78u  IPv4 0xffffff803443f4e0      0t0    TCP 172.20.1.73:59064->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   79u  IPv4 0xffffff8034443500      0t0    TCP 172.20.1.73:59082->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   80u  IPv4 0xffffff8033169320      0t0    TCP 172.20.1.73:59068->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   81u  IPv4 0xffffff8034622de0      0t0    TCP 172.20.1.73:59130->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   82u  IPv4 0xffffff8034629de0      0t0    TCP 172.20.1.73:59119->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   83u  IPv4 0xffffff802e8bba40      0t0    TCP 172.20.1.73:59054->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   84u  IPv4 0xffffff8033131500      0t0    TCP 172.20.1.73:59061->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   85u  IPv4 0xffffff8033139de0      0t0    TCP 172.20.1.73:59071->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   86u  IPv4 0xffffff8033163de0      0t0    TCP 172.20.1.73:59058->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   87u  IPv4 0xffffff802e9cd320      0t0    TCP 172.20.1.73:59096->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   88u  IPv4 0xffffff8034628fa0      0t0    TCP 172.20.1.73:59084->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   89u  IPv4 0xffffff803310a4e0      0t0    TCP 172.20.1.73:59080->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   90u  IPv4 0xffffff802e8ba4e0      0t0    TCP 172.20.1.73:59115->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   91u  IPv4 0xffffff802e8bec20      0t0    TCP 172.20.1.73:59085->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   92u  IPv4 0xffffff802e8bd6c0      0t0    TCP 172.20.1.73:59094->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   93u  IPv4 0xffffff802f6bb6c0      0t0    TCP 172.20.1.73:59138->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   94u  IPv4 0xffffff802e8b16c0      0t0    TCP 172.20.1.73:59117->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   95u  IPv4 0xffffff8033130de0      0t0    TCP 172.20.1.73:59103->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   96u  IPv4 0xffffff8033104160      0t0    TCP 172.20.1.73:59134->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   97u  IPv4 0xffffff802e954fa0      0t0    TCP 172.20.1.73:59104->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   98u  IPv4 0xffffff8033149fa0      0t0    TCP 172.20.1.73:59135->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root   99u  IPv4 0xffffff803312f880      0t0    TCP 172.20.1.73:59114->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  100u  IPv4 0xffffff802e9cc4e0      0t0    TCP 172.20.1.73:59140->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  101u  IPv4 0xffffff8034620320      0t0    TCP 172.20.1.73:59150->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  102u  IPv4 0xffffff803310ec20      0t0    TCP 172.20.1.73:59120->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  103u  IPv4 0xffffff802e9b6320      0t0    TCP 172.20.1.73:59116->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  104u  IPv4 0xffffff802e9cfde0      0t0    TCP 172.20.1.73:59126->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  105u  IPv4 0xffffff8033131c20      0t0    TCP 172.20.1.73:59127->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  106u  IPv4 0xffffff803317aa40      0t0    TCP 172.20.1.73:59183->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  107u  IPv4 0xffffff802f6bcc20      0t0    TCP 172.20.1.73:59129->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  109u  IPv4 0xffffff8033162fa0      0t0    TCP 172.20.1.73:59144->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  110u  IPv4 0xffffff8033144500      0t0    TCP 172.20.1.73:59156->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  111u  IPv4 0xffffff802e998500      0t0    TCP 172.20.1.73:59158->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  112u  IPv4 0xffffff803312f160      0t0    TCP 172.20.1.73:59154->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  113u  IPv4 0xffffff80330f8160      0t0    TCP 172.20.1.73:59185->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  115u  IPv4 0xffffff8033174de0      0t0    TCP 172.20.1.73:59177->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  116u  IPv4 0xffffff802f6c2c00      0t0    TCP 172.20.1.73:59187->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  117u  IPv4 0xffffff803314ade0      0t0    TCP 172.20.1.73:59172->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  118u  IPv4 0xffffff8034441880      0t0    TCP 172.20.1.73:59164->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  119u  IPv4 0xffffff803317d500      0t0    TCP 172.20.1.73:59179->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  120u  IPv4 0xffffff803316a160      0t0    TCP 172.20.1.73:59173->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  121u  IPv4 0xffffff80346226c0      0t0    TCP 172.20.1.73:59196->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  122u  IPv4 0xffffff802f6c6c20      0t0    TCP 172.20.1.73:59170->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  123u  IPv4 0xffffff803310ac00      0t0    TCP 172.20.1.73:59206->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  124u  IPv4 0xffffff80331636c0      0t0    TCP 172.20.1.73:59239->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  125u  IPv4 0xffffff80331306c0      0t0    TCP 172.20.1.73:59242->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  126u  IPv4 0xffffff801434f160      0t0    TCP 172.20.1.73:59215->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  128u  IPv4 0xffffff8033144c20      0t0    TCP 172.20.1.73:59208->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  129u  IPv4 0xffffff8033102c00      0t0    TCP 172.20.1.73:59209->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  130u  IPv4 0xffffff80331604e0      0t0    TCP 172.20.1.73:59233->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  131u  IPv4 0xffffff803461f4e0      0t0    TCP 172.20.1.73:59210->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  132u  IPv4 0xffffff803313a500      0t0    TCP 172.20.1.73:59211->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  133u  IPv4 0xffffff8033150160      0t0    TCP 172.20.1.73:59218->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  135u  IPv4 0xffffff802e03e500      0t0    TCP 172.20.1.73:59213->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  136u  IPv4 0xffffff80330f8880      0t0    TCP 172.20.1.73:59214->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  137u  IPv4 0xffffff8033104fa0      0t0    TCP 172.20.1.73:59241->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  138u  IPv4 0xffffff802e8be500      0t0    TCP 172.20.1.73:59234->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  140u  IPv4 0xffffff802e9524e0      0t0    TCP 172.20.1.73:59235->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  143u  IPv4 0xffffff803314f320      0t0    TCP 172.20.1.73:59237->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  144u  IPv4 0xffffff803316bde0      0t0    TCP 172.20.1.73:59225->172.20.5.7:443 (CLOSE_WAIT)
ocspd     7823           root  145u  IPv4 0xffffff802e03dde0      0t0    TCP 172.20.1.73:59232->172.20.5.7:443 (CLOSE_WAIT)

Hi
Is ther anybody having the same problem?
I still didn't got rid of it.

Similar Messages

  • Slow Performance due to JDBC Version ?

    Technical Support for an application that uses Oracle Spatial data told me that slow application performance could be due to an old version of JDBC drivers. Has anyone else encountered this issue?
    I am using Oracle 8.1.7 Release 3 on Sun Solaris. My application uses the thin Oracle driver that came with the client installation in classes12.zip.
    Is there a better JDBC version for Spatial data?
    Andrew Greis
    FCC/CompuTech

     
    Satellite P55-A5200
    seemed to really slow down to a crawl  ...   Am I looking at virus or bad memory module?
    More likely your hard drive is failing. Multiple read/write attempts slow things down.
    Time to immediately back up everything important. Also, create an image of the drive on an external disk.
    Then run chkdsk /r at an elevated command prompt. It will insist upon rebooting Windows. Reply Yes and restart Windows. Expect this to take quite a while on a 750 GB disk.

  • G5 Tower - Extremely slow performance in Finder, hanging apps

    About the system:
    Power Mac G5
    2 x 2.5GHz CPU
    4.5 GB RAM (physical)
    160 GB HDD (85 GB free - formatted Mac OS Extended Journaled)
    OS 10.4.11 with latest software updates downloaded and installed
    This box is running incredibly sluggish - apps are taking 20+ bounces just to open, as many as 10 to 30 seconds to simply open a folder from the desktop. Even trying to drag a window has a significant delay.
    This all seemed to start when I copied to this machine, a backup of my music files library from an external drive that had been attached to another Mac (Intel Mini) - about 50GB of music, approximately 10k songs. I opened iTunes 8.0.2 (for the first time ever on the G5) and it hung trying to add the new files to the empty library. Since then, the entire machine seems to have been hosed. I realize the iTunes thing might be a red herring, but the problems coincided exactly with the new music and first launch of iTunes.
    Since then, I've tried pretty much everything I could think of - ran the Disk Utility and OnyX utilities (all were clean), zapped the PRAM - even reinstalled Tiger. Same problems. Activity Monitor shows the CPU running at 98% - 99% idle when this is happening (although it takes 90 seconds to open Activity Monitor)and shows 3.92 GB of free RAM. So, the computer doesn't seem to be overworked.
    Any thoughts or ideas would be most appreciated. Unfortunately, AppleCare is no more for this box...

    Since the Power Mac seems to be running normally while booted from the DVD, it must be related to the hard drive in some way. If it has 85 GB of free space, it should not be a problem with lack of free space. If it was me, I would clone (exactly duplicate) the internal drive to an external FireWire drive using Carbon Copy Cloner. Then try to restart from the external drive.
    If things operate normally while booted from the external, the current system installation is fine. I would then reformat (erase) the internal drive using Disk Utility. Then clone the external back to the internal. See if the internal now operates normally. It should. But if it does not, there is probably something wrong with the drive itself (a hardware problem).
    If the problem recurs while booted from the external, there is something wrong with your general system installation. Creating another user account proved that the problem was not isolated to one user. In this case, you have two options. You can reinstall Mac OS X on the internal using the +Archive and Install+ option. This option will retain your user data and settings, but give you a fresh system. In case something bad happens, the clone on the external will serve as your backup. OR you can reinstall Mac OS X using the +Erase and Install+ option. This will give you a completely new installation on an blank volume, and you can migrate your data from the external drive after making sure everything is working normally.

  • Firfox slowing way down or hanging and task manager has multiple sessions of "plugin-container.exe *32" running.

    I'm running Win 7, Firefox 10.0.2 and all my plug-ins are up to date. I'm having issues with Firfox slowing way down or hanging, let say like when going to Youtube or site that just has a picture that uses Flash. I go to task manager and have multiple sessions of “plugin-container.exe *32" running at anywhere from 2,000k to over 300,000k (only one at the larger amount and most at 2m to 8m). I have to kill the multiple processes to get it running right again.

    Hi kb11,
    Have you looked at our [https://support.mozilla.org/en-US/kb/firefox-slow-or-takes-too-long-start performance troubleshooting section]? There is a lot of good information in there that should help.
    Hopefully this helps!

  • My iMac running very slow some times its hang, its happened after I update Lion, please anybody advice me what to do?

    My iMac running very slow some times its hang, its happened after I update Lion, please anybody advice me what to do?

    See:
    Mac Maintenance Quick Assist,
    Mac OS X speed FAQ,
    Speeding up Macs,
    Macintosh OS X Routine Maintenance,
    Essential Mac Maintenance: Get set up,
    Essential Mac Maintenance: Rev up your routines,
    Maintaining OS X, 
    Five Mac maintenance myths, and
    Myths of required versus not required maintenance for Mac OS X for information.

  • Lion: very slow performance of my macbook pro

    very slow performance.
    went to terminal, did the top command, and got following results (mind you, ONLY have Safari and of course Terminal open):
    Processes: 96 total, 4 running, 9 stuck, 83 sleeping, 419 threads      19:07:17
    Load Avg: 1.99, 1.81, 1.59  CPU usage: 2.36% user, 5.21% sys, 92.41% idle
    SharedLibs: 1660K resident, 0B data, 0B linkedit.
    MemRegions: 15947 total, 2662M resident, 47M private, 209M shared.
    PhysMem: 695M wired, 2175M active, 1083M inactive, 3953M used, 13M free.
    VM: 250G vsize, 1093M framework vsize, 699065(68) pageins, 1724738(881) pageouts
    Networks: packets: 70104/55M in, 66648/10M out.
    Disks: 966630/9347M read, 327765/18G written.
    PID   COMMAND      %CPU  TIME     #TH  #WQ  #POR #MREG RPRVT  RSHRD  RSIZE
    4058  top          5.2   00:03.32 1/1  0    28   29    912K   216K   1620K
    4055  bash         0.0   00:00.02 1    0    20   23    356K   216K   1112K
    4052  CVMCompiler  0.0   00:00.30 1    0    30   69    7780K  220K   16M
    4051  login        0.0   00:00.08 2    1    33   63    928K   216K   2184K
    4049  Terminal     0.3   00:01.34 7    3    128+ 164+  7580K+ 13M    15M+
    4042  ocspd        0.0   00:00.02 1    0    26   33    420K+  276K   1376K+
    4041  WebProcess   0.0   00:04.35 7    3    119  201   16M-   10M    26M-
    4039  Safari       1.1   00:09.44 12   3    193  413   47M-   20M    81M-
    3958  spindump_age 0.0   00:00.02 2    2    38   55    356K   220K   1100K
    3956  spindump     1.3   00:42.93 16/1 13   228  145   46M+   15M    53M+
    3953  aosnotifyd   0.0   00:00.18 3    1    53   279   2064K  3532K  6156K
    3939  AddressBookM 6.8   06:59.11 4    1    68   4067+ 2131M- 3308K  1554M-
    3895  lsboxd       0.0   00:00.06 2    2    49   69    1156K  6820K  3292K
    3031  cookied      0.0   00:01.36 2    1    42   82    2028K  268K   3
    every minute or so the computer blocks, every 3 or 4 hours I have to restart etc.
    any suggestions?

    ok, stopped syncing in System preferences and even (horror) deleted the file which reappeared in seconds.
    now waiting to see if stopping the syncing helps - though computer is now working a bit better, the info on Activity Monitor would indicate it is not a real improvement
    473           AddressBookMobileMeSharingAgent          me          1,4          4          1.020,0 MB          Intel (64 bit)
    312           helpd          me          0,4          65          358,9 MB          Intel (64 bit)
    0           kernel_task          root          1,1          76          336,6 MB          Intel (64 bit)
    459           Mail          me          0,4          9          276,2 MB          Intel (64 bit)
    194           java          root          0,1          30          162,4 MB          Intel (64 bit)
    405           Safari          me          0,5          12          120,0 MB          Intel (64 bit)
    407           Safari Web Content          me          0,2          7          100,3 MB          Intel (64 bit)
    195           WindowServer          _windowserver          0,5          7          64,4 MB          Intel (64 bit)

  • T42 hangs, extremely slow performance

    Hello,
    I can boot up my T42, but it works very slowly.  In safe mode with networking, it works great.  I have automatic updates turned on, but it cannot successfully download updates.  It still has service pack 2.  Not sure if that's related to slow performance.

    Hello,
    I can boot up my T42, but it works very slowly.  In safe mode with networking, it works great.  I have automatic updates turned on, but it cannot successfully download updates.  It still has service pack 2.  Not sure if that's related to slow performance.

  • Slow performance of discoverer portlets

    Hi,
    I am running into slow performance of a particular page in portal, there are multiple sites hosted on the portal but these all have static text and are very quick to load but the one page with discoverer portlets and a web-clippping portlet is taking ages. If I run these reports on their own they are instant. Has anyone had similar problems with 9.0.2 portal and the discoverer reports ? I tried to identify a particular report that may be the culprit by deleting them one by one and to no avail. After a few hours effort I found the design mode was hanging as well. Again, just for this 1 page.
    There are 3 tabs on this page with about 4 report portlets and 1 web-clipping portlet.
    Thanks for any help,
    Brandon

    Thanks for the help.
    Seems to have been resolved although I'm not sure if thats the end of the story. Will wait and see.....
    So far apparently a port conflict of some sort in the discoverer config was causing it to hang and then also other system demands on the network and server housing the discoverer end-user layer were also causing problems.
    No error messages unfortunately......

  • Slow performance on a iMac 27" (maybe originated by the HDD)

    Hello,
    Well, I've had my iMac for 10 months now, but have never really paid attention to its performance since it was my first Mac and I was upgrading from a quite old computer, so it obviously proved to be a far superior machine.
    However, I noticed the problem when I started to be more critical with my machine's performance (this triggered by the fact that I bought, some months after, a MacBook Air which flies beyond time and space). Curious about this, I requested a friend to do a benchmark test with Xbench resulting in his machine (another iMac 27” with comparable specs) clearly outperforming mine. Even the Air, with its slower processor and smaller RAM, has a relatively close performance.
    Additionally, I have started to notice how the computer takes a long time to start-up and, after the desktop is “layed out”, it takes a lot of time before the machine becomes “responsive” (I usually try to start Mail and Google Chrome as soon as the pointer pops in!) with the final result that I have to wait in company of the beach ball for quite some seconds (half a minute) and even after the application had started, I can still hear the HDD working it as if there would be no tomorrow! And then, it is slooooow. Funnily enough, “tougher” applications like Photoshop or Illustrator don’t seem to have as many problems, relatively speaking.
    A little bit on the background info: I have two partitions: one for Bootcamp (since I was migrating from Windows, I had some software that I wanted to use there: Matlab and Office, basically, and then some smaller Windows-only programs).
    Derived from the benchmark test, I think I might have isolated the problem to the HDD (not sure though!).
    SO THE QUESTIONS ARE:
    1. How can I verify that the slow performance is due to the HDD being defective/badly configured/etc.?
    2. Has the Windows Bootcamp Partition any effect on my machine’s performance under MacOS? (I would assume not, but you never know!). I have more than 1.3 TB free space left
    3. What kind of corrective measures should I take?
    4. Any other type of advice will be warmly welcome: I will try to do some PRAM and SMC resets but I am not counting on it. I had also ran the disk utilities and there were no permission errors (not so sure what this means, but I’ve read that it is supposed to be good news.)
    5. Any extra info you might need, lemme know!
    Greetz,
    Víctor.
    PS: Sorry for the loooong post. I tried to be thorough!

    1. How can I verify that the slow performance is due to the HDD being defective/badly configured/etc.?
    Run Apple Hardware Test: http://support.apple.com/kb/HT1509
    2. Has the Windows Bootcamp Partition any effect on my machine’s performance under MacOS? (I would assume not, but you never know!). I have more than 1.3 TB free space left
    Probably not but 1.3TB of free space left on the total HD is not enough for OS X, OS X needs a minimum of 10-15% free space! If you mean 1.3TB of Windows space I'd recommend posting that question in the Boot Camp forum.
    3. What kind of corrective measures should I take?
    If the drive is failing per the AHT then it's covered by warranty and will need to be replaced. Remember back up!!!!!!!!!!
    4. Any other type of advice will be warmly welcome: I will try to do some PRAM and SMC resets but I am not counting on it. I had also ran the disk utilities and there were no permission errors (not so sure what this means, but I’ve read that it is supposed to be good news.)
    Can't hurt, make sure you read the instructions carefully and execute the tests exactly as they are described for Intel based iMacs.
    5. Any extra info you might need, lemme know!
    If you no longer have a need for Windows on your iMac I'd recommend removing that partition using Boot Camp Assistant. That may correct your problems.
    I would also recommend checking if System Preferences - Startup Disk and see if your internal HD is highlighted as the Startup Disk.
    In addition I would recommend checking your Login Items (System Preferences - Accounts - Login Items) and delete any applications you don't need launching at Login.

  • Slow Performance Forms 10g !!!!

    Hi,
    I have migrated several forms from 6i to 10g and i use a 11g Database.
    Most of the users accessing from different countries complain of slow performance but the basic idea of migration is to get a better performance. My users mostly work on laptops.
    I am unable to find where the problem is. Is this might be due to network traffic since they are accessing via internet or any server related issues. Please help me to find and fix the problem and is there any tips for gaining better performance in using forms 10g.
    Regards,
    Suresh

    So, were they running on 6i via laptop and accessing via the internet before you migrated ? (ie: was it 6i client server or 6i web forms)
    Did you migrate the database too ?
    Slow performance as in : it used to be seconds and now it's taking minutes ?
    Steve

  • Slow performance with 2 new full T1 installed .

    We've just added second Full T1 line to
    this router to dedicate full T1 bandwidth our two database servers.We are still experiencing the slow performance to our remote location such as file copying and acceessing applications.below are configs and sh run.Any help and inputs are greatly appreciated.Is the router configuration correct? or need to be modified.Thanks
    Danny.
    router2621xm#sh run
    Building configuration...
    Current configuration : 1924 bytes
    version 12.3
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    service udp-small-servers
    service tcp-small-servers
    hostname OPS
    boot-start-marker
    boot-end-marker
    enable secret xxxx
    enable password xxxx
    no network-clock-participate slot 1
    no network-clock-participate wic 0
    no aaa new-model
    ip subnet-zero
    ip cef
    no ftp-server write-enable
    class-map match-any VOIP
    match ip dscp ef
    policy-map VOIP-QOS
    class VOIP
    priority 1158
    class class-default
    fair-queue
    random-detect dscp-based
    interface FastEthernet0/0
    ip address 192.168.157.1 255.255.255.0 secondary
    ip address 192.168.7.1 255.255.255.0
    ip policy route-map policyroute speed auto
    full-duplex
    no mop enabled
    interface Serial0/0
    ip unnumbered FastEthernet0/0
    service-policy output VOIP-QOS
    no ip mroute-cache
    interface Serial0/1
    ip unnumbered FastEthernet0/0
    service-policy output VOIP-QOS
    no ip mroute-cache
    router eigrp 15
    network 192.168.1.0
    network 192.168.2.0
    network 192.168.3.0
    network 192.168.4.0
    network 192.168.5.0
    network 192.168.6.0
    network 192.168.7.0
    network 192.168.8.0
    network 192.168.151.0
    network 192.168.152.0
    network 192.168.153.0
    network 192.168.154.0
    network 192.168.155.0
    network 192.168.156.0
    network 192.168.157.0
    network 192.168.158.0
    network 192.168.201.0
    no auto-summary
    ip classless
    ip route 0.0.0.0 0.0.0.0 192.168.1.5
    no ip http server
    access-list 150 permit ip host 192.168.7.5 any
    access-list 150 permit ip host 192.168.7.6 any
    access-list 151 permit ip any any
    dialer-list 1 protocol ip permit
    route-map policyroute permit 10
    match ip address 150
    set interface Serial0/1
    route-map policyroute permit 20
    match ip address 151
    set interface Serial0/0
    line con 0
    line aux 0
    line vty 0 4
    password xxxx
    login
    end

    A couple of items worth noting are the QOS policies themselves.
    This is OK
    class-map match-any VOIP
    match ip dscp ef
    Add this
    class-map match-any VOIP-signalling
    match dscp af31
    match dscp cs3
    Change the policy-map to reflect the changes
    policy-map VOIP-QOS
    class VOIP-signalling
    bandwidth 16
    class VOIP
    priority 24
    class class-default
    fair-queue 256
    random-detect dscp-based
    The bandwidth is meant for 4 concurrent phone conversations so adjust up as needed. The priority is based on my own testing so take it as you may.
    The most important statement is "fair-queue 256", by default you only get 16 queues. Allowing for 256 queues only uses a modest amount of memory so its a simple low impact choice for the router and allows more conversations between devices without interruption.
    Upping the number of queues in your policy would be the best and most important item for your performance problem, next of couse to coercing EIGRP to load balance the T1s properly.
    Brian
    P.S. Create a loopback interface for the ip unnumbered use, cause if the Fa0/0 goes down everything goes down and you can't telnet in from anywhere to look at it. Eliminate the following items from the config by using "no" in fromt of them, a bit of research will tell you why, and start you toward eliminating a few other items.
    service udp-small-servers
    service tcp-small-servers

  • Slow performance of PreparedStatement

    I am having difficulty with extremely slow performance or a relatively simply Microsoft SQL Server 2000 call from my Java applet. Most of the application runs fine, but there are certain parts that are repeatedly giving me a long delay before completing their execution. The code is as follows:
    // Create the try block for the execution of the SQL code
            try{
                // Create the command to be executed
                String command = new String( "select Description, Enabled " );
                command += "from tLineInfo where( Line = ? )";
                // Create the SQL text to be executed
                PreparedStatement get = _connection.prepareStatement( command );
                get.setInt( 1, lineNo );
                // Execute the SQL command
                ResultSet lineInfo = get.executeQuery();
                // Display the information accordingly
                if( lineInfo.next() ){
                    // Populate the user data fields
                    description.setText( lineInfo.getString( "Description" ) );
                          <! more display code here >
    }   // End of if statment
                else{
                    // Clear the user data fields
                    description.setText( " " );
                           <! more display code here >
                }   // End of else statements
                // Close the result set in preparation for the next query
                lineInfo.close();
            }   // End of try block
            catch( Exception e ){
                // Display a dialog box informing the user of the problem
                Object[] options = { "     OK     " };
                JOptionPane.showOptionDialog( null, e.getMessage(),
                        "Error",
                        JOptionPane.OK_OPTION, JOptionPane.ERROR_MESSAGE,
                        null, options, options[ 0 ] ); 
            }   // End of Exception catch
            // Get the related area information
            populateAreaCombo( lineNo );       
    private void populateAreaCombo( int lineNo ){
            // Format the areaComboBox
             try{
                // Create a command to get the devices from the database
                String command = new String( "select Area, [Name], [Description] " );
                command += "from tAreas where( Line = ? )";
                // Create the SQL statement to grab the information, and
                // populate the search parameter
                PreparedStatement getAreas =
                        _connection.prepareStatement( command );
                getAreas.setInt( 1, lineNo );
                // Execute the command
                ResultSet areas = getAreas.executeQuery();
                // Loop through the result set, and add collect the areas
                Vector< String > controlAreas = new Vector();
                while( areas.next() ){
                    // Add the area to the comboBox
                    controlAreas.add( Integer.toString( areas.getInt( "Area" ) ) +
                            " - " + areas.getString( "Name" ) + ": " +
                            areas.getString( "Description" ) );
                }   // End of while loop
                      <! more display code here >
                    The application always seem to pause at the second PrepraredStatement call:
    PreparedStatement getAreas =
                        _connection.prepareStatement( command );This seems to be a very simple operation, and it is not even the execution of the query where the long delay is realized. Rather, it is in the actual creation of the object prior to the execution.
    The delay is very repeatable at this exact statement each time.
    Additionally, of interest, is that the delay is only realized on computers remotely connected to the database. If I run this code on the localhost, then there is no delay. As soon as I distribute it, then the delay is incurred. That being said, there is not a network related issue that I can identify here. I have even isolated the server to be on the network with just one other PC, and the delay still persisted.
    Does anyone have any ideas?
    Thanks

    I can determine where the delay occurs by adding
    dialog boxes at a bunch of different steps, then
    monitoring them for when they appear; a little
    archaic, of course, but an easy way to find this
    out.You should
    1. Get the start time
    2. Get the current time at each step.
    3. Print the results at the end.
    4. Repeat a number of times to average.
    >
    When you say that I should not mix database code with
    display code... What exactly do you mean? To be
    more precise in my description, I was simply setting
    a bunch of different text fields and/or check boxes,
    etc., based on the result set returned. It was not
    as if I was creating a portion of the GUI there or
    something. I am assuming that is an allowable
    practice...
    You should have a class that does nothing but the database work. That class should be used by other classes (like classes that do GUI.)
    I have made little effort to close my resources, and
    sometimes they are not closed at all. When you say
    "resources", what exactly do you mean by that? Are
    you referring to the result sets, for example? I do
    not know of other resources that need to be closed,
    except for the connection to the DB itself. This, I
    have as persistent throughout the duration of the
    user's session.
    You must close result sets, statements and connections. They must be closed in that order.
    I am not running this code on the Internet, but it
    has been designed to be run on a small corporate
    network ( < 10 users). This is why I opted for the
    applet to run the entire application through instead
    of doing more HTML work.That is ok.

  • Tips For Solving the Mac OS X Lion Slowness (Lots of Beach Balls)

    Hi Folks,
    Just a quick list of tips for this issue that some of Mac OS X Lion users face.
    The main symptom is that we get the Beach Ball on almost any task, it takes 4, maybe five times more time to do what we need to do. So depending on the schedule, it can drive us crazy. I was facing that, and started to think that Lion was a Windows Vista relative.
    Please remind that the tips below involve backing up and restoring your system. If you are not careful, you may lose everything. You are responsible for your acts. Be cautious!
    How I solved my issue:
    1) Checked for Disk Permissions and the Disk itself:
    - Applications / Utilities / Disk Utility:
    - Click on your disk, and then VERIFY DISK. If everything is OK, move on. If it is not, REPAIR DISK.
    - Now click on VERIFY DISK PERMISSIONS. If everthing is OK, move. If not, Repair.
    This step 1 is to make sure that your slowness is due to something related to the OS itself and not to permissions/disk.
    If this solves the slowness, then you are OK. Now further steps are necessary. In my case, this just helped a little bit. The beach-balling reduced by 20% only. Still too slow.
    2) Do a full backup of your system.
    I used Time Machine. Make sure you have all of your applications closed. So the backup will be full. If you fail to do a good backup, you will lose everything! Make sure you do a good one. Maybe do it twice on 2 different disks! Now you have been warned.
    3) Do a Full Restore of your entire system.
    Now, get that Install CD that came with your Mac,
    - Put it on your drive, shut down your computer.
    - While holding the C key, press the start button of your Mac. It will boot using the Install CD that came with your Mac.
    To recover your entire system:
    Connect your Time Machine backup disk to your computer. If you’re restoring your system because of a problem with your startup disk, make sure the disk has been repaired or replaced.
    Insert your Mac OS X Install disk, and double-click the Install Mac OS X icon.
    In the Installer, choose Utilities > Restore System from Backup.
    In the Restore Your System dialog, click Continue.
    Select your Time Machine backup volume.
    Select the Time Machine backup you want to restore.
    Follow the onscreen instructions.
    4) Remove the CD, and boot.
    When I did that, the system came back very fast and responsive. No more beach balls (only on the really-intensive tasks), and everything was back to normal.
    5) So, what was it anyways?
    Before doing this Backup/Restore, I was getting lots of DISK I/O ERRORS, specially during boot time (you can check that by shutting down your mac, powering it back on and imediatelly pressing Command-V - Verbose Mode).
    Sure, the first thing in mind was that I had a faulty hard drive, but I checked it several times for errors (via Disk Utility), and nothing showed up.
    So I decided to do a full backup/restore of the system. And it solved it, at least for me.
    My config:
    MacBook Pro (2009 edition) - 5 GB RAM - 640 GB HD - Mac OS X 10.7
    Regards.

    Also my mac will not complete my 5 software updates, no idea which software, but it said it could not do it. Also backing up with time machine had failed twice today. Thanks

  • Powerbook painfully slow performance

    Recently my powerbook has been running unusably slow. Here's a timeline:
    - Noticed slow opening of applications, saving, switching from application to application, browsing folders through finder.
    - Computer kept freezing after 1-10 minutes of use.
    - Checked RAM in system profiler - 1GB RAM showing 512 MB.
    - Removed RAM and restarted (new RAM being sent to me at present).
    - Freezing problem stopped. Slow performance improved for 2-5 minutes after startup but after 10 minutes, back to same old slow usage.
    - Checked hard drive, repaired permissions, did macjanitor cleanup.
    - Hardware check from startup DVD showed no problems. SMART check OK'd hard drive.
    - Archive and re-install tiger and updated to 10.4.9.
    - Activity monitor shows %CPU usage as fairly normal. Kernel_task is using about 720MB of virtual memory under very light/no user usage.
    - Created a new user and performance normal in new user, leading me to believe that the problem is related to user library and possibly preferences.
    - Put preferences folder on desktop and started putting my preferences back into user library folder bit by bit, restarting and testing. The performance would be better each time but hard to test as I have to wait at least 10 mins to test each time - time consuming business.
    Is there any way to narrow down which preference file is causing the problem without painstakingly re-adding preference files one by one to the user library folder, waiting 10 mins and testing?
    Otherwise, could the diagnosis above be due to something else all together. Been through the discussions and can't get anything to work so far. The RAM was the cause of the freezing problem, but seems to have brought on the slowness problem.
    Any help would be much appreciated, thanks Graeme.

    Graeme:
    If you have not done so recently run Unix Maintenance (CRON cleaning). Download and install MacJanitor and run all tests.
    Dr. Smoke's FAQ Tuning Mac OS X Performance has some hints you may find helpful.
    Regualar maintenance also helps performance. Take a look at the following articles:
    Mac OS X 10.3/10.4: System maintenance
    Macintosh OS X Routine Maintenance
    Maintaining OS X
    Good luck.
    cornelius

  • Oracle Collaboration Suite Slow Performance

    Hi,
    I have encountered with problem with OCS 10.1.2 with following information:
    Hardware : DL-380G5
    Operating System : OEL 4 update 5 64 bit
    Oracle Product : Collaboration Suite 10.1.2
    The installation has been done in three server as follow:
    Server 1: Application Tier (OCS component such as mail, calendar , discussion , ...)
    Server 2: Infrastructure (Oracle Single Sign on)
    Server 3 : Infrastructure (Oracle Internet Directory)
    Patch Information : Cumulative Patch 10.1.2.4 (Note: 406284.1) + Mandatory Patch after 10.1.2.4 ( Note:
    423515.1) + Patch 10.1.0.5 on Infrastructure layer
    have been applied on Application tier and Infrastructure.
    Problem_ Everything goes well after reboot of all 3 servers and refresh but after 2 hours nobody can
    connect to OCS services due to slow performance
    Only restarting the servers cause the users can connect to OCS services again.
    Any Idea will be appreciated.
    Edited by: Oralinux on Oct 29, 2009 5:08 PM

    Did you ever find out why this was happening? We seemed to have developed a similar issue and we have had a Severity 1 level SR for 4 days now and no one seems to able to work it out.
    cheers
    paul

Maybe you are looking for