Big Data 2 min read

A Year with Prestissimo: How Meta Leveraged Velox for Presto Vectorization

The article summarizes a PrestoCon talk that reviews Meta's year‑long production experience with Prestissimo—a C++ Presto worker built on the Velox execution engine—highlighting its architecture, integration design, performance gains, and lessons for anyone considering Velox‑based vectorization.

Past Memory Big Data
Past Memory Big Data
Past Memory Big Data
A Year with Prestissimo: How Meta Leveraged Velox for Presto Vectorization

Prestissimo is an ambitious project that rewrites the Java‑based Presto worker in C++ by leveraging the open‑source execution engine Velox. The presentation first outlines Velox’s architecture and its components, then describes the high‑level design of integrating Velox into Presto (Prestissimo).

After more than a year of production deployment at Meta, the authors share observations gathered from experimental platform workloads, including performance benefits and practical lessons. The material is intended for teams looking to raise Presto performance or to consider “veloxification” of their own query engines.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

C++prestoVectorized ExecutionveloxMetaprestissimo
Past Memory Big Data
Written by

Past Memory Big Data

A popular big-data architecture channel with over 100,000 developers. Publishes articles on Spark, Hadoop, Flink, Kafka and more. Visit the Past Memory Big Data blog at https://www.iteblog.com. Search "Past Memory" on Google or Baidu.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.