On Tuesday, June 16, 2015 at 11:35:40 AM UTC-4, Matthew Krick wrote: > > I've read everything I could on deployment options, but my head is still a > mess when it comes to all the choices, especially with how fast julia is > moving! I have a website on a node.js server & when the user inputs a list > of points, I want to solve a traveling salesman problem (running time > between 2 and 10 minutes, multiple users). Can someone offer some advice on > what's worked for them or any pros/cons to each option? Least cost is > preferable to performance. >
Well I can offer some information about the thing I know the most about (node-julia). Ironically, I'm also working on visualizing the TSP, but more single user oriented currently. In this case, seems like a reasonable approach is routing the user request (via express) and calling your Julia code, process that asynchronously, and long-poll for the result. That part at least is straightforward. The tricky part is the long running time, and process queue, once Julia becomes multithreaded, then this becomes much less of an issue, but until then there are tasks, which is complicated with libuv use. But if there is little likelihood of 2 users running things simultaneously that's much less of a issue. Interesting problem; willing to help out if needed.
