Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restructure entrykvs #26

Open
lordfeck opened this issue Jul 31, 2021 · 1 comment
Open

Restructure entrykvs #26

lordfeck opened this issue Jul 31, 2021 · 1 comment

Comments

@lordfeck
Copy link
Owner

Currently we heap all entries under %entryKvs like follows:

$entryKvs{KEY_NAME} => { ... }

Each entry exists directly under here. The category name is a field for the entry.

We could optimise performance and readability if we restructured storage to work as follows:

$entryKvs =>$categoryName => $entry

We could simply call 'keys' for the category name nested under the entrykvs, this would return a list of categories for easier processing. Likewise we could get all the entries for each category. This saves effort in the long run and thus seems more like True Perl (TM).

@lordfeck lordfeck added this to the R3 milestone Jan 2, 2022
@lordfeck
Copy link
Owner Author

lordfeck commented Feb 6, 2022

We look up entries by key name alone in more than a few places, so shelve this for now unless performance becomes a demand (i.e. processing thousands of entries) and we're then checking every entry for a matching category

@lordfeck lordfeck removed this from the R3 milestone Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant