Comparing
fixing_dbt_is_incremental
(85a9821
) withmain
(982b3f7
)-3%
- Untouched
- 6
- Skipped
- 6
This run is associated to a commit that was force-pushed
It will not be associated with its branch history. Be careful when comparing its performance to other runs.No successful run was found on main ( 7dfaa46) during the generation of this report, so 982b3f7 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.
Benchmarks
12 total
from_parent
crates/lib/benches/depth_map.rs::benches::depth_map::DepthMap+1%
160.7 µs159.2 µs
fix_superlong
crates/lib/benches/fix.rs::benches::fix0%
466.1 ms464 ms
fix_complex_query
crates/lib/benches/fix.rs::benches::fix0%
34.2 ms34.2 ms
parse_expression_recursion
crates/lib/benches/parsing.rs::benches::parse-3%
23.1 µs23.9 µs
parse_complex_query
crates/lib/benches/parsing.rs::benches::parse-5%
15.1 µs15.8 µs
parse_simple_query
crates/lib/benches/parsing.rs::benches::parse-9%
3.4 µs3.8 µs
The benchmarks below were skipped, so their baseline results are used instead. If they were deleted in your codebase, archive them to remove them from the performance reports.
Learn more about archiving benchmarks
Learn more about archiving benchmarks
from_parent
crates/lib/benches/depth_map.rs::benches::depth_map::DepthMapSkipped
345.5 µs*
parse_complex_query
crates/lib/benches/parsing.rs::benches::parseSkipped
44.7 µs*
fix_complex_query
crates/lib/benches/fix.rs::benches::fixSkipped
38.6 ms*
parse_simple_query
crates/lib/benches/parsing.rs::benches::parseSkipped
19.4 µs*
fix_superlong
crates/lib/benches/fix.rs::benches::fixSkipped
698.6 ms*
parse_expression_recursion
crates/lib/benches/parsing.rs::benches::parseSkipped
69.9 µs*
Commits
Click on a commit to change the comparison rangeBase
main
982b3f7
-2.74%
fix: is_incremental work properly
85a9821
13 days ago
by benfdking