Stats

  • State Not Answered
  • Replies 5
  • Subscribers 44
  • Views 7404
  • Members are here 0
More Content

Orcad Capture performance

Cantstandya

Hi all,

In my company we are more and more struggling with bad Orcad Capture performance on our PCs. Capture becomes laggy when wiring and takes long time to boot. This affects indirecly our product quality as we are constanly distracted by the lagging. Boot time is around 2 minutes with license selection window popping up. Booting is a bit quicker when having selected default license suite earlier, but still boot can take around 1 minute.

Opening a ~15MB DSN file at home through VPN from a network drive at work is impossible. Then Capture lags for 5 minutes and the capture.exe process is not responding according to the task manager. A 15MB file should be fairly easy to handle these days - unless the SW is poorly written or something.

It seems to me that Orcad Capture is affecting the multitasking performance of Windows. Sometimes when Capture is lagging some other programs are lagging/hanging as well. Could there be som old 16/32 bit drivers in Capture messing up the Windows multitasking? Actually Capture is hanging right now and the Notpad++ program I am drafting this post in is also lagging(!). They are greyed out, showing not responding in Task manager and I get a spinning mouse wheel.

Our PCs seems to get more and more laggy the longer since last PC reboot. This could be due to the PC itself. Not sure if this is due to Capture. Maybe a combination. A PC reboot makes the performace normally a bit better.

We are running Lenovo X1 Gen9 16GB RAM. We are not hitting the roof on disk, memory or CPU at all. But it seems to be something in the background that messes stuff up.

We are running 17.4 hotfix 37. I just tried 23.1 now, but no noticable improvement.

We have tried to disable all autoloading tcl files, but doesnt seem to improve the performance.

There seems to be some suspended capture.exe processes piling up in the task manager. I am not able to kill them. Right now I have five. Could this be a symptom of something?

Someone else struggling with this?

Parents
  • Cantstandya
    0

    I have done some more checking and to me it seems that the issue in general is disk accesses. We are typically running across VPN from home to a network drive with the DSN on it. The VPN connection has a latency of around 50ms. Capture seems to more or less hang for all disk accesses. So during saving/autobackup we experience lag/hanging. Due to this we are now working with DSN files locally on C:. This improves things a lot.

    One thing I see is that Capture is accessing the reports file that I have in my project very often. Capture can go from really responsive to almost constant hang when having 3-4 reports files attached to my project(BOM, DRC files etc). Looking into Wireshark I see that Capture accesses these files(SMB2 packets over VPN to network drive) almost constantly when I do various stuff in Capture. So when Capture seems to hang for each disk access these accesses slows down performance a lot. I think also these accesses slightly slows down wiring in Capture when working on a DSN on local C: drive, which could be very annoying.

Reply
  • Cantstandya
    0

    I have done some more checking and to me it seems that the issue in general is disk accesses. We are typically running across VPN from home to a network drive with the DSN on it. The VPN connection has a latency of around 50ms. Capture seems to more or less hang for all disk accesses. So during saving/autobackup we experience lag/hanging. Due to this we are now working with DSN files locally on C:. This improves things a lot.

    One thing I see is that Capture is accessing the reports file that I have in my project very often. Capture can go from really responsive to almost constant hang when having 3-4 reports files attached to my project(BOM, DRC files etc). Looking into Wireshark I see that Capture accesses these files(SMB2 packets over VPN to network drive) almost constantly when I do various stuff in Capture. So when Capture seems to hang for each disk access these accesses slows down performance a lot. I think also these accesses slightly slows down wiring in Capture when working on a DSN on local C: drive, which could be very annoying.

Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.