Socket read in RPC Broker takes CPU cycles
Bug #321745 reported by
jeff.apple
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenVista/GT.M Integration |
Fix Released
|
Undecided
|
jeff.apple | ||
Bug Description
Connecting with a CIS client results in each READ command continuously consuming 3%-9% CPU. This does not include the activity resulting from CIS's heartbeats.
Test system: GT.M V5.3-003 on Ubunutu 8.10 guest in VirtualBox 2.1.2, Windows XP Pro host.
Related branches
| description: | updated |
Revision history for this message
| jeff.apple (jeff-apple) wrote | #1 |
Revision history for this message
| jeff.apple (jeff-apple) wrote | #2 |
| Changed in openvista-gtm-integration: | |
| assignee: | nobody → jeff-apple |
| status: | New → Confirmed |
Revision history for this message
| jeff.apple (jeff-apple) wrote | #3 |
| Changed in openvista-gtm-integration: | |
| status: | Confirmed → Fix Committed |
| Changed in openvista-gtm-integration: | |
| milestone: | none → phase-1-alpha |
| Changed in openvista-gtm-integration: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Run the routine: D ^READTEST(9191), then telnet to that port. Top will show CPU use for the blocked read.