Thread hogging behaviour when training a classification/regression model

The "thread hogging" behaviour of the JS client API is problematic as it blocks the whole interface. This is a problem with a severity level between Major Usability problem and Usability catastrophe (Nielsen), observed with high frequency between different actions and users.

For instance, one participant, decided to move away from using the JS client library to trying to use a server side implementation (which also was problematic on its own). It would be beneficial to explore a Web-worker implementation to surpass this problem.

Recommendation: Pursue a design pattern in which there are two learning modules (i.e., two classification modules, or two regression modules) one on the regular JS client code, another on the web-worker code. The web worker code receives training data from regular code, trains the model, and exports the JSON model to the regular JS code model, that loads it and runs test data with it.