Slow rendering of diagrams

[djeang]

Question

Hi,

I am evaluating structurizr-onpremise version 3208 using the Docker image. The rendering of simple diagram is quite slow, making the product practically not usable. That's even worse when deploying it on our openshift cluster.

Is it possible I miss a specific setting or so ? I didn't see anything related to this in documentation.

Kind Regards

[simonbrowndotje]

You'd need to provide some specific examples I'm afraid. Diagram rendering is done client-side (i.e. in your web browser, via a JavaScript library) and it can struggle with larger diagrams, but this will be unrelated to your OpenShift cluster. Automatic layout is typically applied on the server-side via Graphviz, so poor performance of this could be related to the resources you've allocated. You will also see a difference between storing workspaces on the file system vs using an S3 compatible service too.

[simonbrowndotje]

Are you using autolayout or the default set of views? If so, the on-premises server will be trying to load the themes when applying automatic layout ... and the delay will likely be caused by a slow network or a lack of Internet access (in which case you're seeing the TCP timeout). Do you see anything like this in the server logs?

[djeang]

Indeed, I use autolayout.
I check the logs but I don't see any related to TCP timeout (using default loggig settings).
Anyway, it may be nice to display an error balloon, when something wrong happens.

[djeang]

To me, it would make sense to embed the default theme in the application to avoid delay. Also users don't expect the default theme changing without explicitly upgrading the app.

[simonbrowndotje]

I have added some code to ignore the pre-built themes, since they are not required for applying automatic layout -> c626228

This is now available in build 3244+.

[djeang]

Thank you Simon,

Works great !

[djeang]

Works great.