= 27d567bc2d48d9f40e9ccc20ea370b15)
gjm comments on Open thread, Jul. 11 - Jul. 17, 2016 - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (131)
We did some benchmarks. Sometimes we did it well, sometimes not that well.
For example in the case of Job Shop Scheduling benchmark we were unable to break a single record. There are records waiting to be break in JSS area, but we haven't broken a single one.
But we are still holding some (years old) packing records right now.
One may say, that JSS is the base of every scheduling and that packing is not. In fact, the real life scheduling is more complicated than either one of those benchmarks. We have many more constrains in real life. And it turns out, that many constrains somehow help the evolution to find trade-offs.
if you're the holders of some records for certain problem types then that grabs my interest.
I'd suggest leading with that since it's a strong one.
Not necessarily for their target market.
I belief that being flexible about target markets is one of the major ways businesses grow.