first-time-bucket default value slows down tests.
See original GitHub issueLagom sets the default value of
cassandra-query-journal {
first-time-bucket = "20160225T00:00"
}
An integration test running over a clean database takes quite some time to converge from that value to now()
. We should document how to hack your unit tests to take that setting to a value that speed up test.
For example, I’ve set first-time-bucket = "20190903T00:00"
on a test today shaving around 20 seconds (from 50sec to 30sec)!
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Troubleshoot slow or inconsistent speeds when downloading ...
For a test that resembles requests to Amazon S3, be sure to run a TCP traceroute or mtr to the Regional endpoint of...
Read more >sql - TimeScaleDB - Time bucket query slow with indexes and ...
The dataset I am using is market tick data for one particular date for which I have loaded around 84 million records into...
Read more >Testing best practices - GitLab Docs
Optimize factory usage. A common cause of slow tests is excessive creation of objects, and thus computation and DB time. Factories are essential...
Read more >Improve Data Flow Performance with SSIS AutoAdjustBufferSize
The Test Results ... We can see that enlarging the buffers from the default values to 20MB and 30,000 rows already had a...
Read more >Date histogram aggregation | Elasticsearch Guide [8.5] | Elastic
Like the histogram, values are rounded down into the closest bucket. ... As always, rigorous testing, especially around time-change events, will ensure that ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I will have two of these, please.
Could akka-persistence-cassandra do the
now()
iffirst-time-bucket
is unset and the database is clean, and then that seed value be obtainable later? Seems silly to have a database at hand and have to record this in a file while generating a project (seeing as it’s not a secret password-like thing).