query edit metadata functions are syncronized, should only be per query instance

Description

<cfscript> a = queryNew( "id,name" ); loop times="10"{ r = queryAddRow( a ); querySetCell(a, "id", r, r) } // all these underlying methods are syncronized queryAddColumn( a,"type" ); queryDeleteColumn( a, "type" ); m = getMetadata( a ); QuerySort( a, "id", "desc" ); queryDeleteRow( a ); </cfscript>

https://github.com/lucee/lucee-testlab/blob/main/custom/benchmark/tests/query-manipulation.cfm

Environment

None

Attachments

6
  • 26 Dec 2024, 10:00 pm
  • 25 Dec 2024, 05:19 pm
  • 25 Dec 2024, 04:08 pm
  • 25 Dec 2024, 04:08 pm
  • 25 Dec 2024, 04:08 pm
  • 25 Dec 2024, 04:08 pm

relates to

Activity

Show:

Zac Spitzer 26 December 2024 at 22:00
Edited

definitely much better, with this new report I’ve knocked up on test lab

https://github.com/lucee/lucee-testlab/actions/runs/12508557915/attempts/1#summary-34897096020 (scroll down)

the numbers in each cell are min/avg/max

image-20241226-220025.png

Zac Spitzer 25 December 2024 at 17:19

those were with 5k, with 25k it’s better

image-20241225-171849.png

Zac Spitzer 25 December 2024 at 16:08

interesting, mixed results… GHA runners differ

 

image-20241225-160508.png
image-20241225-160525.png

but on the specific test, not so conclusive?

image-20241225-160546.png
image-20241225-160617.png
Fixed

Details

Assignee

Reporter

Priority

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Created 25 October 2024 at 11:19
Updated 29 December 2024 at 11:12
Resolved 26 December 2024 at 22:00

Flag notifications