Socket read in RPC Broker takes CPU cycles

Bug #321745 reported by jeff.apple on 2009-01-27
2
Affects Status Importance Assigned to Milestone
OpenVista/GT.M Integration
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.

jeff.apple (jeff-apple) on 2009-01-27
description: updated
jeff.apple (jeff-apple) wrote :

Run the routine: D ^READTEST(9191), then telnet to that port. Top will show CPU use for the blocked read.

jeff.apple (jeff-apple) wrote :

Questions were sent to FIS about this issue.

Changed in openvista-gtm-integration:
assignee: nobody → jeff-apple
status: New → Confirmed
jeff.apple (jeff-apple) wrote :

Add device parameter to slow down polling rate in read

Changed in openvista-gtm-integration:
status: Confirmed → Fix Committed
Jon Tai (jontai) on 2009-05-02
Changed in openvista-gtm-integration:
milestone: none → phase-1-alpha
Jon Tai (jontai) on 2009-05-02
Changed in openvista-gtm-integration:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments