HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
YelpArchive
MOE
C++2014–2019
YelpArchive / MOE · Archived

MOE

A global, black box optimization engine for real world metric optimization.

3Distinct people
10Mentions
0Explicit recommenders
1.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A global, black box optimization engine for real world metric optimization.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2014-07-24 16:07:40 UTC to 2019-01-28 20:04:28 UTC.

01232014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC211
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC202
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

What Hacker News says

10 sources
To be fair, the hyperparameter tuning behind these AutoML systems are getting fairly robust. Google bases theirs on Vizier [0]. The Amazon Sagemaker group has people from the gpyopt project [1]. There is also tons of open source projects out there to help for non-enterprise projects [2] [3]. There are also stand-alone companies that help with this explicitly for enterprises [4] (Caveat, I am a founder). Increasingly I think more time will be spent on the creative/bespoke aspects you mention later in your post, like making sure that you are building a system that actually achieves some business value (vs just getting a better academic-oriented metric result). Hyperparameter tuning is basically trying to do high-dimensional, non-convex optimization on time consuming and expensive to sample functions. Hand tuning is a terrible way to approac
Read the rest
h this, and is different for each problem as you point out. Experts can leverage their domain expertise and the unique aspects of their data, models, and applications in much better ways. [0]: https://www.kdd.org/kdd2017/papers/view/google-vizier-a-serv... [1]: https://github.com/SheffieldML/GPyOpt [2]: https://github.com/Yelp/MOE [3]: https://github.com/hyperopt/hyperopt [4]: https://sigopt.com
In Your AI skills are worth less than you think
SigOpt (YC W15) is a related service that performs a superset of these features as a SaaS API (I am one of the co-founders). We've been solving this problem for customers around the world for the last 4 years and have extended a lot of the original research I started at Yelp with MOE [1]. We employ an ensemble of optimization techniques and provide seamless integration with any pipeline. I'm happy to answer any questions about the product or technology. We're completely free for academics [2] and publish research like the above at ICML, NIPS, AISTATS regularly [3]. [1]: https://github.com/yelp/MOE [2]: https://sigopt.com/edu [3]: https://sigopt.com/research
In Google Vizier: A Service for Black-Box Optimization
Yes, but does it work? I cannot tell from reading the introductory materials whether it will actually search efficiently over large space (where it is computationally expensive to evaluate the fitness of any individual point). I know that folks are having some success with Gaussian process optimisation for hyper parameter tuning (eg https://github.com/Yelp/MOE), but I would be sceptical about the application of genetic programming to this area, particularly as broadly defined a search space as TPOT seems to set up (genetic programming either doesn't make assumptions about the objective function being optimised which can be used to search more efficiently, like Gaussian optimisation does - or uses implicit assumptions that may be unsuitable, depending on how you want to think about it); has anyone seen benchmarks against other search metho
Read the rest
ds? The workflow does look great though - integrating it into scikit looks really clever.
In Introducing FBLearner Flow: Facebook's AI Backbone
As you pointed out, it is all about a balance, and every feature has different tradeoffs. SigOpt was designed to unlock the power of Bayesian optimization for anyone doing machine learning. We believe that you shouldn't need to be an expert and spend countless hours of administration to achieve great results for every model. We're wrapping an ensemble of the best Bayesian methods behind a simple interface [0] and constantly making improvements so that people can focus on designing features and their individual domain expertise, instead of needing to build and maintain their own hyperparameter optimization tools to see the benefit. For experts who want to spend a lot of time and effort customizing, administering, updating, and maintaining a hyperparameter tuning solution I would recommend forking one of the open source packages out there l
Read the rest
ike spearmint [1] or MOE [2] (disclaimer, I wrote MOE while working at Yelp). [0]: https://sigopt.com/docs [1]: https://github.com/JasperSnoek/spearmint [2]: https://github.com/Yelp/MOE
In Unsupervised Learning with Even Less Supervision Using Bayesian Optimization
We've found that SigOpt compares very well to spearmint, as well as MOE [1], which I wrote and open sourced around the same time spearmint was open sourced. We have a paper coming out soon comparing SigOpt rigorously to standard methods like random and grid search as well as other open source Bayesian methods like MOE [1], spearmint, HyperOpt [2], and SMAC [3] with good results. [1]: https://github.com/Yelp/MOE [2]: https://github.com/hyperopt/hyperopt [3]: http://www.cs.ubc.ca/labs/beta/Projects/SMAC/
In Unsupervised Learning with Even Less Supervision Using Bayesian Optimization
Depending on how long it takes to "evaluate the goodness of a solution" techniques like multi-start gradient decent can rapidly become intractable though, especially in higher dimensions. There are a handful of open source libraries out there that try to tackle this time consuming and expensive black box optimization problem from a more Bayesian approach [1] [2]. There's also a YC company to do this as a service (full disclosure, I'm a co-founder) [3]. Combining these methods with TensorFlow could be very powerful and is one step closer to more automatic ML flows though. [1]: https://github.com/Yelp/MOE (full disclosure, I co-wrote this) [2]: https://github.com/hyperopt/hyperopt [3]: https://sigopt.com/cases/machine_learning
In TensorFlow: open-source library for machine intelligence
Thanks for the feedback! We'll update the post to be more clear about this. Our goal was to make this as simple and accessible as possible and in doing so we may have cut out too much. I'll try to make this more clear. SigOpt [0] vs OSS: We are similar to hyperopt, spearmint, and MOE [1], which we developed at Yelp and also uses Gaussian Processes to do Bayesian Global Optimization. SigOpt extends and expands upon our work on MOE while wrapping everything in a simple API [2] and web interface. One thing we learned while promoting MOE was that many people have this problem, but few have the time or expertise to get these expert level open source tools running properly, so we built SigOpt to bring these powerful tools to anyone via a simple API. [0]: https://sigopt.com [1]: https://github.com/Yelp/MOE [2]: https://sigopt.com/docs
In Tuning machine learning models
There are a variety of different techniques that solve similar problems. We have some of them documented here: http://yelp.github.io/MOE/why_moe.html#other-methods (including these two), but would love to add more. Each one has different tradeoffs depending on what your problem entails, what license you can use and what platform you are running on. Many of these methods have been around for some time. The seminal paper was published in 1998: http://www.ressources-actuarielles.net/EXT/ISFA/1226.nsf/0/f... MOE provides many interfaces (REST, Python, C++), a permissive license (Apache v2) and allows for many optimal points to be quickly queried at once, non-sequentially (Expected Parallel Improvement), along with a slew of other features. We have also tried to follow strict software engineering principles throughout (testing, docing, etc). W
Read the rest
e are always looking to improve though and are taking pull requests and suggestions for improvements! https://github.com/Yelp/MOE/issues
In Show HN: Moe, a Metric Optimization Engine

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.