A fast, performant analytics experience is the foundation for a premium product experience in customer-facing analytics. Speed up dashboards built on top of any data source by enabling our out-of-the-box Warp acceleration layer, which is designed to further accelerate query performance on larger amounts of data stored in non-analytical (e.g. transactional) data sources.
Activate Warp on a selected data source with one simple click. Warp will accelerate querying while keeping your data automatically in sync at the frequency you specify. During the acceleration, data is loaded in our optimized-for-speed analytical data store in the chosen data tenancy (EU or US). Data is removed from our store upon deactivation of Warp.
Warp can be activated on any database or plugin dataset. Note that Warp isn’t available for local files and web service connectors, because these datasets are already stored in our analytical data storage.
Only an owner of a dataset can activate Warp on a dataset, and indicate/update its synchronization schedule (i.e. when a dataset should be synced, and how often). This feature can be disabled/enabled per user via a feature flag called flag_acceleration (check out this article for more explanation on how to set up feature flags).
To activate Warp, simply open your dataset of choice, hit 'Activate' in the top-right corner, and set your sync frequency. That's it! Lightning-fast dashboards are waiting for you in the Luzmo app.⚡
Warp offers two powerful sync modes to ensure your source data remains consistent with the accelerated data store, while optimizing performance and resource usage.
✅ Small to medium-sized datasets.
✅ Cases where e.g. frequent schema changes can be expected.
⚠️ Can be slow and resource-intensive for large datasets.
⚠️ Limited to maximum one sync per day.
✅ Large datasets that require frequent updates.
✅ Use cases where near real-time data access is essential.
⚠️ Requires timestamp columns (created_at, updated_at, deleted_at) to track changes.
⚠️ Some schema changes may require a Full Sync to maintain integrity. If frequent schema changes are expected, Full sync (or real-time querying without Warp) might be a more suitable solution for your use-case.
Note: If you switch between Full Sync and Delta Sync, a Full Sync is automatically triggered to ensure data integrity.
Warp Delta Sync allows you to update your dashboards as frequently as every 30 seconds, providing near real-time data updates without overloading your database.
Syncing smaller data increments instead of full datasets lowers query load on data source, improved bandwidth usage, optimized infrastructure usage.
To activate Warp Delta Sync, your dataset must include:
🔑 A unique identifier column (e.g., id or primary key) – Needed for updates and deletes to work correctly.
Note: Composite keys (multiple columns as a unique identifier) are also supported (up to 3 columns).
📊 At least one timestamp column (created_at, updated_at, deleted_at) – Required to track changes in data. The available sync modes are dependent on the types of timestamp columns your dataset contains:
created_at column.created_at and updated_at column.created_at, updated_at, and a deleted_at column.If your dataset does not meet these requirements, Warp Delta Sync will not be available, and a Full Sync will be required instead.
By default, Warp sync frequency is set to:
You can freely choose any frequency equal to or greater than 1 day (day, week, month, quarter, year)
⏱️ If you’d like to use faster sync frequencies (e.g., hours, minutes, or seconds), please reach out to cs@luzmo.com to enable high-frequency options.
Warp synchronizes your entire dataset or just the changes into a data store hosted by Luzmo. Queries to populate dashboards are launched against this accelerated store, with syncs happening at the defined frequency.
Query caching, on the other hand, stores the results of specific queries temporarily. This means:
By combining Warp Delta Sync with query caching, you get both faster queries and up-to-date data.
Yes, you can choose between Full Sync and Delta Sync in your dataset settings. However, switching between modes will trigger a Full Sync to ensure data integrity.
Warp Delta Sync includes retry mechanisms and error handling. If a sync fails:
If you are using a Warp full sync (without Delta) and change some columns in the data source, you can use the “Trigger manual full sync” button in order to trigger a metadata sync, If you are using Warp Delta sync and:
Yes! If your dataset does not have the required timestamp columns, you can still use Warp with Full Sync. This allows your source data to still be periodically synchronized (overwriting any previous sync’s data), but can only be configured with sync intervals up to once every day.
By default, we inform you via email if your accelerated dataset could not be synced or if the sync is delayed. If data stays out of sync for 1.5 times the synchronization schedule (e.g. data is not updated after 1.5 days when the data should be updated every day), an email will be sent to the owner(s) of the dataset. If you want to opt out of those emails for all WARPed dataset that you own, you can do so on your Profile page in the Notifications section.