Hi,
I'm sending info which I collected/remember when performance issue mentioned in Roadmap discussion happened.
I think, as a user, I can declare myself as a tester of Sculpt. I had it running with uptime for about three weeks till today. Unfortunately I was forced to reboot due to some strange global performance issues. I can try to help in the future in diagnosing such issues by providing some data in case there is a need for it.
The next time you observe such an anomaly, it would be good to have a look at the top tool or to enable the trace-logger option to observe the CPU utilization, hoping for clues.
I have made a photo of top from that episode. Let me know if next time you'd prefer to get different view to get different set of information.
top
It would also be interesting to see if the issue disappears when restarting the VM.
It did not help. I have tried that.
Before stopping virtual machines working in system shell was hard because even listing files took seconds. When I stopped virtual machines the situation improved but as soon as I tried to start them again, system has become unresponsive again. Then I rebooted.
I also have a copy of /report/log from that time, but I don't see anything suspicious there. By the way it would be useful if there was some kind of timestamp with log (it doesn't have to be a real time). Trying to correlate information from log with the performed actions is hard if you do not have any information about "age" of each log.
I don't expect much, but hopefully it will give you some useful information - even if only ideas how to improve such process of gathering information for similar events in the future.
Regards
Tomasz