Closed dmarkh closed 1 month ago
If my math is correct, tofINLSCorr is ~60MB per record: 30000 1024 2 = 61,440,000 (and only 2048 bytes per db row). If I remember correctly, that table from 2009 was replaced with the optimized version because it was too slow.
Now, eTOF has ~4MB per entry (equals to db row) = 1,000,000 * 4, which is a single 4MB chunk and is going to be handled very differently at the DB level... Let's see how it goes.
-Dmitry
On Wed, Oct 2, 2024 at 12:13 PM Gene Van Buren @.***> wrote:
@.**** approved this pull request.
Pretty straightforward.
Considering that I get a single instance of the Calibrations_tof / tofINLSCorr is approximately 1 GB, it seems likely to me that 4 MB entries should not be an issue.
— Reply to this email directly, view it on GitHub https://github.com/star-bnl/star-sw/pull/712#pullrequestreview-2343431799, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHWGXQDBOAQO7ZP2YB4RINDZZQLSTAVCNFSM6AAAAABPH5U26OVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGNBTGQZTCNZZHE . You are receiving this because you authored the thread.Message ID: @.***>
Sorry, you are correct: 60 MB for the tofINLSCorr table (1 GB was after this converted into a CINT text file, so lots of bytes unassociated with the actual payload). Thanks for the correction and additional comments, Dmitry.
-Gene
Subj. A new Offline DB table was created for Yannick. Let's see if 4MB records are manageable... https://drupal.star.bnl.gov/STAR/subsys/etof/etof-database-tables/etof-get4state