Improve performance of DB Metadata impl

[wezell]

When rolling out the metadata changes, we provided two impls, one a fs based impl and one a db impl. The DB impl was intended to be our default impl because it helped lower our dependency on the NFS share but we found that in actuality, it caused a bottleneck because it had to do a DB lookup, then write a temp file before it could return the metadata.

We should improve/tune up this impl so that it can become our default impl and just return the metadata using a single db query without having to write a tmp file.

[wezell]

Link to subfeature: https://dotcms.productboard.com/feature-board/planning/features/14928643

[jdotcms]

Waiting for Fabro's QA

[fabrizzio-dotCMS]

PR is #22834

[fabrizzio-dotCMS]

I performed a load test using the tool called "siege"
https://medium.com/@guy.callaghan/load-testing-with-siege-3fa6a1e8118d
Feeding it with a file with 103 transactions. Each transaction is meant to generate metadata for 50 different binaries.
metadata-load-testing.txt

The test environment was seeded with 5300 separate file assets
the test was executed against both implementation DB vs FILE_SYSTEM in 3 rounds. On every round, the intermediary files were completely removed and the whole cache was flushed.

the results can be seen here https://docs.google.com/spreadsheets/d/1Qr0EByhNI_RUmtmhd8D6_oXRB0B24dQFyr8zaXq9Ako/edit#gid=0
But in summary

apparently now it is cheaper to copy the previously generated metadata from the database using the intermediate files than generating them directly from felix and then putting them as files and then also in the cache.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.