Rhino SystemInfo reporting question

Rhino
1

Though sometimes my help is probably not all that helpful, I still utterly fail to understand why SystemInfo does not report the CPU model name as part of the information.

While not too much should not have theoretically changed in Rhino 8, even from my own experience, it seems to be much better at hammering its single or couple of threads on the CPU.

While often the GPU is an automatic target (with good reason), can someone explain why the CPU is missed? Also, in the era where it is often important to have reasonably balanced systems, ReBar, stable RAM configs (EXPO or XMP), etc… I don’t understand why this information is just left to guessing or asking the user.

As we get closer and closer to things like realtime rendering, live material editing, and other good tools, should CPU, Chipset, and RAM config be reported? Is it felt that for hardware that the GPU is so dominant that the CPU doesn’t matter?

1 Like
2

Hi David -

FWIW, I never find myself asking a user for their CPU information. It’s not as if they can simply install new drivers to make a problem go away.

Perhaps this information might be useful for rendering people? @nathanletwory?
-w

3

The #1 cause of random crashes is old video drivers or hopelessly obsolete or misconfigured video hardware. Nothing else really matters. An obsolete CPU will just be slow, a “bad” one will just not work.

4

I understand.

I suppose it was more sometimes in relation to Rhino 8 recently. There is a lot of “slowness” with how it is working, but with some people unable to observe this behavior at all. I was wondering if there is now really a point where there are now CPUs which are marginally able to shove the Rhino 8 demand through in good time. On the face of it, there are clear Rhino 8 problems remaining. However I also wondered if there was a realistic chance that CPU has started to matter in some cases which are not obvious to everyone.

However, if this is not the opinion or likelihood, then of course the matter can be closed.

Thanks!

5

I don’t know, our rendering solution works best with GPUs. Those, together with their drivers, cause most of the problems. I don’t know what we would do with CPU information - we already report amount of RAM. And CPU isn’t typically causing trouble like we see with GPUs.

You can always a feature request against the SystemInfo subsystem in YouTrack .