Many nodes make loading the model exremely slow

Question

question

Dj Moens asked Nov 11 2020 at 2:35 PM Phil BoBo commented Nov 11 2020 at 3:47 PM

Many nodes make loading the model exremely slow

Hi,

We ran into an issue regarding network nodes. A model containing over 8100 nodes (90x90) takes an awfull long time, whereas a model with about 2500 (50x50) is still reasonable. Attached is a model that cretes a node grid you can use to test. It almost look like it takes quadratic more time as a funtion of the number of nodes instead of linear extra time as would expected..

Is there an internal issue that it takes that long for larger networks. And can it be resloved is there be a workaround?

Rgds

DJ

Testnode2500.fsm

Software Version:

FlexSim 20.0.7

flexsim 20.0.7 networknodes

testnode2500.fsm (1.6 MiB)

· 8

Phil BoBo ♦♦ commented · Nov 11 2020 at 2:44 PM

My assumption is that you are talking about the time to calculate the distance table. The network navigator uses Dijkstra's algorithm to calculate the amount of time to get from each network node to each other network node and stores that in its distance table, so that it can quickly calculate travel paths when the model is running. Thus the size of that table is numNodes * numNodes, so if you are making a grid, then that's gridSize ^ 4.

If you are making a grid of nodes, why are you even using network nodes? If you want a grid of locations that can be used for traveling, use A*. A* is literally a grid.

0 ·

Dj Moens Phil BoBo ♦♦ commented · Nov 11 2020 at 2:49 PM

Sorry Phil,

Pressed sent too soon. It is loading of a saved model that takes very long.

Rgds

DJ

0 ·

Dj Moens Phil BoBo ♦♦ commented · Nov 11 2020 at 2:50 PM

It is not the issue of the grid, this was more of an example.

0 ·

Dj Moens Phil BoBo ♦♦ commented · Nov 11 2020 at 2:58 PM

Oh and Dijkstra also does not seem to be the issue as creating the paths reset and run is fast.

I expected the network that contains 4 times as many nodes to load just 4 times slower, but it is much more order 4^2 (16..?)

0 ·

Jason Lightfoot ♦♦ Dj Moens commented · Nov 11 2020 at 3:07 PM

reset after creating 8100 nodes was really slow for me.

1 ·

Show more comments

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2020-11-11T15:38:37Z

Phil BoBo answered Nov 11 2020 at 3:38 PM

I found the issue.

The problem is that the OnOpenModel scripts are explicitly calling optimizenetwork() in MAIN:/project/events/OnOpenModel/refresh stuff.

I'll take that line out for the next bugfix release (as the network itself is handling that in its own resetVariables and doesn't need to be explicitly called by the model open scripts.)

If you want to fix it in the meantime, you can make a module that replaces that node with a version without the optimizenetwork() call.

· 2

question