As one of the largest shared mobility networks, Lyft connects millions of people with the transportation services they need every single day, from ride services to bike and scooter rentals.
But Lyft doesn’t just cater to those on the move—they also offer an opportunity to millions of drivers across the U.S. and Canada to earn money on their own schedules.
To sustain their widespread operations, Lyft uses mathematical optimization to facilitate logistics, incentive allocation, market design, pricing levels, and more.
Since adopting Gurobi as their primary optimization solver, Lyft has seen exponential efficiency gains that have changed the way they’re able to plan out operations.
As independent contractors, drivers using Lyft are in control of when and how they drive. Lyft’s role is to enable them to be successful with timely, accurate information on market balance.
One way to influence positive market outcomes is by providing driver incentives and showing drivers how they can increase their earnings.
“An example that most riders are familiar with is Prime Time, which raises prices when the demand for rides exceeds driver supply,” explains Chris Sholley, Senior Director of Lyft Driver Earnings. “That’s one way for us to manage the health of the marketplace. But when we initially launched it, one of the biggest complaints from drivers was that the Prime Time levels change too frequently. So we developed a Prime Time equivalent for the driver’s side, Bonus Zones. This allows drivers to see the incremental money they can earn on a ride, represented visually on a map.”
The challenge for Lyft, however, lies in determining the optimal level, location, and duration of the zones.
Under another incentive, drivers can receive a bonus after reaching a milestone, such as completing a certain number of rides in a week. But after how many rides? And how much should that bonus be? For help answering these questions, Lyft sought an optimization solver.
Sholley had prior experience with Gurobi as a college student and appreciated its seamless integrations, so when it came time to shop software vendors, he knew where to start.
Lyft’s optimization problems involve millions of variables and constraints, and they need a solver that allows them to converge on a solution within a limited amount of time.
In the past, the Driver Earnings team had tried a variety of solvers, including commercial and open-source options. But when it came to speed, they found the best results with Gurobi.
“In the end, we found that in most instances, Gurobi was the most efficient,” says Sameer Manek, Senior Staff Data Scientist on Lyft’s Driver Earnings team. “One of the big advantages was that Gurobi for Python has a matrix-based API, which allowed us to express our problem a lot more naturally—because a lot of our modeling is in matrices, so being able to express it in matrices as well just made it more seamless.”
In addition to better computation times, the Lyft team has found that Gurobi is also easier to use compared to other options. “We have some new products that we are still in the process of launching, and we can very quickly and easily prototype optimization algorithms for those using Gurobi,” says Abbas Bozorgirad, Data Science Manager on the Lyft Driver Earnings team. “And it does a very good job, enough that the initial prototype could basically stay in production.”
Bozorgirad says that although Lyft could likely use other algorithms to find an optimal solution, Gurobi offers the fastest—and most reliable—route. “Besides speed, we can also be confident that we’re taking the optimal approach,” he explains.
Since making Gurobi the primary solver for their driver incentive optimization problems, Lyft has reduced their time spent per linear problem by 80% and improved their overall end-to-end time by 92%.
Those efficiency gains have allowed Lyft to plan ahead more effectively, which offers them a competitive advantage and enables them to adjust to market changes more rapidly.
“One thing that has been easier to do with Gurobi—mostly because of the speed-ups—is that we can pre-populate multiple scenarios, and plan and revise with shorter timelines,” explains Manek. “So rather than needing to think about how many minutes or hours of lead time we need, we can shrink that down, which gives us more time to iterate.”
Prior to using Gurobi, when Lyft would near its deadlines for notifying drivers of upcoming incentives, they would often have to settle for suboptimal plans in order to give drivers adequate notice. But now, they have much more time and flexibility.
And because Lyft is better able to plan, they’re also able to think about different types of incentives more jointly.
“Rather than thinking about these incentives in isolation, we’re able to coordinate more easily across Bonus Zones or weekly ride goals,” Manek says.
As for future plans, one goal that Lyft would like to continue pursuing with Gurobi is an ability to plan incentives around various degrees of uncertainty. “We might not know exactly when the Taylor Swift concert is going to end, or if there’s going to be a rainstorm in Buffalo next week,” says Manek. “But our goal is to make our incentive decisions with an awareness of those variables.”
With Gurobi, Lyft can continue improving their planning processes and incentive programs without the negative effects of vendor sprawl because they have everything they need in one solver.
As Sholley explains, “Gurobi is a competitive piece of software—it can solve many different optimization problems. So rather than trying to find a set of solvers, you really can make Gurobi your one-stop shop.”
GUROBI NEWSLETTER
Latest news and releases
Choose the evaluation license that fits you best, and start working with our Expert Team for technical guidance and support.
Request free trial hours, so you can see how quickly and easily a model can be solved on the cloud.
Cookie | Duration | Description |
---|---|---|
_biz_flagsA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_pendingA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_sid | 30 minutes | This cookie is set by Bizible, to store the user's session id. |
ARRAffinity | session | ARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user. |
ARRAffinitySameSite | session | This cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session. |
BIGipServersj02web-nginx-app_https | session | NGINX cookie |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
_biz_nA | 1 year | Bizible sets this cookie to remember users’ settings as well as for authentication and analytics. |
_biz_uid | 1 year | This cookie is set by Bizible, to store user id on the current domain. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect a user's first pageview session, which is a True/False flag set by the cookie. |
_mkto_trk | 2 years | This cookie is set by Marketo. This allows a website to track visitor behavior on the sites on which the cookie is installed and to link a visitor to the recipient of an email marketing campaign, to measure campaign effectiveness. Tracking is performed anonymously until a user self-identifies by submitting a form. |
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
doc_langsBB | 1 year | Documentation system cookie |
doc_version | 1 year | Documentation system cookie |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
whova_client_id | 10 years | Event agenda system cookie |
Cookie | Duration | Description |
---|---|---|
_gat_UA-5909815-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
Cookie | Duration | Description |
---|---|---|
_an_uid | 7 days | 6Sense Cookie |
_BUID | 1 year | This cookie, set by Bizible, is a universal user id to identify the same user across multiple clients’ domains. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gat_UA-* | 1 minute | Google Analytics sets this cookie for user behaviour tracking. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores the true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInSessionSample_* | 2 minutes | Hotjar cookie that is set to determine if a user is included in the data sampling defined by a site's daily session limit. |
_hjRecordingEnabled | never | Hotjar sets this cookie when a Recording starts and is read when the recording module is initialized, to see if the user is already in a recording in a particular session. |
_hjRecordingLastActivity | never | Hotjar sets this cookie when a user recording starts and when data is sent through the WebSocket. |
_hjSession_* | 30 minutes | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjSessionUser_* | 1 year | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjTLDTest | session | To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails. |
6suuid | 2 years | 6Sense Cookie |
AnalyticsSyncHistory | 1 month | LinkedIn cookie |
BE_CLA3 | 1 year 1 month 4 days | BrightEdge sets this cookie to enable data aggregation, analysis and report creation to assess marketing effectiveness and provide solutions for SEO, SEM and website performance. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
dj | 10 years | DemandJump cookie |
djaimid.a28e | 2 years | DemandJump cookiean |
djaimses.a28e | 30 minutes | DemandJump cookie |
li_gc | 5 months 27 days | LinkedIn Cookie |
ln_or | 1 day | LinkedIn Cookie |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
__adroll | 1 year 1 month | This cookie is set by AdRoll to identify users across visits and devices. It is used by real-time bidding for advertisers to display relevant advertisements. |
__adroll_fpc | 1 year | AdRoll sets this cookie to target users with advertisements based on their browsing behaviour. |
__adroll_shared | 1 year 1 month | Adroll sets this cookie to collect information on users across different websites for relevant advertising. |
__ar_v4 | 1 year | This cookie is set under the domain DoubleClick, to place ads that point to the website in Google search results and to track conversion rates for these ads. |
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
_te_ | session | Adroll cookie |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
li_sugr | 3 months | LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |