You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have each run of getLabels to be saved as {labelName}.json {labelName}.csv
Might be a major QOL improvement to consolidate into a single file?
address:{'name':NAMETAG, 'label':LABEL}
Might need to take a look into the size of all label information and whether it makes sense to leave it in a single large JSON file or into a DB (SQlite perhaps?)
The text was updated successfully, but these errors were encountered:
2.7mb space taken. Don't think it justifies usage of DBMS since we can simply load it into memory once and get object of interest. Since we are using address:nameTags format retrievals should be O(1) as well.
Currently we have each run of getLabels to be saved as {labelName}.json {labelName}.csv
Might be a major QOL improvement to consolidate into a single file?
address:{'name':NAMETAG, 'label':LABEL}
Might need to take a look into the size of all label information and whether it makes sense to leave it in a single large JSON file or into a DB (SQlite perhaps?)
The text was updated successfully, but these errors were encountered: