Size and data rows Limitations

Help
, , ,
1

I saw some posts regarding this, but could not find a real answer. Does anybody know what the known limtations are for models?

I have uploaded an existing situation with only 85mb NWD file. The datastructure is somewhat messy, but there is not really much data in it.

This model just keeps freezing:

image
image875×368 5.92 KB

Normally we work with files from 10mb up till 4.5GB in NWD, so this 80 ish mb model is very low.

Model federation can be a workflow, but not if the files and datatable rows cannot exceed a certain amount.

For reference, our models in ACC work like a charm. Only downside there is that the powerbi connection is not yet available for navisworks files.

2

Hey @Joschy ,

This is a hardware limitation. Assuming this screenshot if from Power BI, your Power BI is running out of memory because the data you are trying to load is too big for Power BI to handle.

3

No this screenshot is from the webviewer (in chrome)

I did not start testing in PowerBi because it didnt work in the webviewer

4

I see my memory go to aproximately 6GB and then it chrashes (my system has 128GB). Also I think for a model of 80mb to go to 6GB that would be weird I guess.

When we know the limitations we can make a modelfederation to adress this issue i suppose. But probably there are other factors why this happens?

5

This is, unfortunately, known. Funnily, you might have better luck with Firefox.

First things first: we’d love to look at that navis file - would you be able to share it with us confidentially? A link to it would also help to understand if this is also, by any chance hardware specific.

Parotting what @alex has debugged endlessly: we’re allocating memory too fast, and on top of that, when we load objects we not only load their display values but as well their associated properties. That & speckle data’s layout is generally geared towards individual object access, so it’s more heavy.

The good news is that @adamhathcock is working on OL2 (object loader 2) which has had so far quite good results on models previously throwing this error, so we’d love to test this against your navis file.

1 Like
6

Hi Dimitrie,

I already have a project set up with @jonathon for an other issue, i dont know if that maybe also can be used for this? Otherwise if you give me a location were the Navis file can go, let me know.

I looked at the model and it has 85.000 objects in it (selection in navisworks set to geometry) so that is not that much i guess (seen other models here with way more objects).

The part that maybe is doing something to the overal loading of the model in the webviewer are the big surfaces with a lot of triangles:

image
image1501×1091 380 KB

I will also test it with more things of to iron out what is taking up the memory I guess.

1 Like
7

It seems that the surfaces are not the problem, I just uploaded a new version with only 80 objects, but with the big meshes, and it went through in a couple of seconds:

image
image1191×682 55.4 KB

1 Like
8

Furhter testing gives me that when having about 50.000 to 55.000 objects in the NWD file (all files come from Civil3D, selection in navis set to geometry) the webviewer is out of memory. So I assume this is the limit for now, also dependant on how much actual data properties are connected to these geometry objects of course.

This upload is done without the option ‘Preserve Model Hierarchy’ which is maybe needed to get all data into Speckle for various reasons. Probably with this option enabled the objects will be less than the 50.000…