Minimum hardware requirements for client-side rendering on the HOOPS Web Platform?

I have started using the HOOPS Web Platform and I can’t find what kind of hardware requirements are needed to interactively render 3D graphics (at any scale) on the client side.

Any help would be appreciated!

Well, it certainly depends on the nature of the data rendered. You can imagine there will be different requirements for rendering a Lego brick vs. a Boeing 777.

Client-Side Rendering (CSR) uses WebGL in the browser and sufficient client-side hardware (GPU) to render the data you expect to view.

Good information Gabe. I wanted to add a bit more information that might be useful for those trying to come to a conclusion on this topics. General hardware requirements for server side rendering are really tricky to come up with because they are specific to each application and use case. The link that @gabriel.peragine posted mentions a few “must haves”, which include:

  • You have sufficiently high network bandwidth to serve 3D model data in an acceptable amount of time
  • The client device has enough computational power and GPU capability to properly render 3D models
  • The client browser supports WebGL

Note, that even if you have an internet connection, a GPU, and ability to render WebGL with your browser, that doesn’t necessarily mean you’ll be able to meet the required performance for your application and/or users. For example, if your user base is largely using tablets in a high latency internet area, then rendering very large assemblies in a time that is acceptable for your end user is probably not going to work. However, in that same use case, the workflow might be that the user identifies single parts and loads them in the field, so waiting a handful of seconds to load a single part or sub assembly is probably not an issue.

The advice our Consulting team generally gives Partners and prospects is to look at performance holistically which includes typical client hardware and software, typical internet connectivity speeds, typical data sets used/loaded, and the desired workflow for you application. After that has all been established you’ll try and make hardware recommendations based on those requirements. Generally you can expect to satisfy 80+% of your users and performance requirements using this approach, and then you can fall back on server side rendering, caching and loading SCS files, and other application specific strategies like on demand loading for the rest of your users.


1 Like