Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: how about promote efficiency in this way ? #2

Open
garview opened this issue Jul 25, 2016 · 0 comments
Open

Suggestion: how about promote efficiency in this way ? #2

garview opened this issue Jul 25, 2016 · 0 comments

Comments

@garview
Copy link

garview commented Jul 25, 2016

I tested the ClashDetectionService time consuming with MEP.ifc which in "IFC-files-master". It tooke over 150s.

It consist of client.getModel(...)——30s, offlineGeometryGenerator.generateForAllElements(pluginManager)——120s and clashDetector.findClashes()—— 15s.

Now I get the model Object by DownloadByOidsDatabaseAction.execute() which could get the model Object within 1s. Also, the model has contained geometry info and no need to call the "offlineGeometryGenerator.generateForAllElements(pluginManager)".
Of course, the ClashDetectionService Plugin didn't call the method "generateForAllElements" except in test method. But it wouldn't work without the call in BimServer1.4-2015-11-04 ——uhm, yeah……I ran the code in 1.4 after some modify.

This means the ClashDetectionService time consuming will be within 20s which the original time consuming over 150s.

Is there a problem with this idea?@rubendel
kind regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant