Can Ciscoview cause high cpu spikes?

Question

I was using LMS 3.2, Ciscoview to open a view on a 6500 that has 2 WS-SUP720-3B supervisors and is running s72033-adventerprisek9_wan-mz.122-33.SXH4.bin.
The device was taking a bit to open up, so I clicked it a couple more times and a couple of minutes later it finally opened.
At the same time I had a telnet session to the device and noted thru sh proc cpu sorted that the SNMP ENGINE had spiked to 95% utilization.
Could Ciscoview be the cause of this? I have found through testing that multiple clicks can cause a small cpu jump (6% - 12%) but I haven't yet reproduced the 95% utilization I saw that day.
Is there an initial discovery that Ciscoview first does to gather it's information that's more intensive than subsquent polling?
-Dave

Answer 1

A couple more questions. Does Ciscoview perform snmpwalks or snmpgets on the device when it is the first time it's contacting it? In the trace logs, I noted:
2009/10/16 22:07:42 EDT TRACE CvDevice: Orig Device Info:
id=192.168.255.21, ipAddr=/192.168.255.21
2009/10/16 22:07:42 EDT TRACE CvDevice: New Device Info:
id=192.168.255.21, ipAddr=192.168.255.21
2009/10/16 22:07:42 EDT TRACE CvDevice: Opening device
192.168.255.21_
polling interval=60...
2009/10/16 22:07:42 EDT TRACE Vector: Getting existing CT....
2009/10/16 22:07:42 EDT TRACE Vector: Index of matched CT is -1
2009/10/16 22:07:42 EDT TRACE Vector: Containment tree not found in the
cache
2009/10/16 22:07:42 EDT TRACE Util: Request: ReqId=47, Cmd=Get,
Session=192.168.255.21Session,
I've noted in attempts to open a device the first time, it takes awhile to open which I'm assuming is the snmpwalk/gets being performed on the device to update its cache. When is this cache cleared? On server reboot?