huge difference in performance using emscripten

[czc98]

Hello!
I have successfully exported meshlib function using emscripten, but there is a huge difference in calling fillHole in js.
In js, it cost 4000ms, and in MeshInspector, it cost 0.4sec.
I applied the -Os option when emscripten compiled.

MR::Mesh mesh_clone;
mesh_clone.addPart(this->mesh);

std::vector<MR::EdgeId> holeEdges = mesh_clone.topology.findHoleRepresentiveEdges();
if (holeEdges.size() != 1)
    return NULL;
MR::EdgeId a = MR::extendHole(mesh_clone, holeEdges[0], MR::Plane3f::fromDirAndPt(MR::Vector3f(n.x, n.y, n.z), MR::Vector3f(p.x, p.y, p.z)));

auto start = std::chrono::high_resolution_clock::now();
MR::FillHoleParams params;
params.metric = MR::getUniversalMetric( mesh_clone );
MR::fillHole(mesh_clone, a, params);
auto end = std::chrono::high_resolution_clock::now();
std::chrono::duration<double, std::milli> duration = end - start;
std::cout << "Elapsed time: " << duration.count() << " ms\n"; // 4000ms

Mesh *res = new Mesh();
res->mesh.points = std::move(mesh_clone.points);
res->mesh.topology = std::move(mesh_clone.topology);

return res;

[czc98]

I also tried it on the MeshInspector web and it only took 0.4 seconds.
Do I need to turn on any options to achieve the same performance?

[Grantim]

Hello! Could you please specify a bit more how have you compiled and exported the function. Have you used MeshLib building scripts?

[czc98]

I've solved this by adding -pthread to the compile option.