#5740 - Analyse use of fields in database for possible optimisation

  • By
  • Added
  • 3 views
Identifier #5740
Issue type Feature request or suggestion
Title Analyse use of fields in database for possible optimisation
Status Open
Tags

Roadmap: Over the horizon (custom)

Handling member Deleted
Addon core_database_drivers
Description It may be possible to optimise some of the fields using the integer database type to use one that requires less bytes (e.g. smallint / mediumint). Have a look through the schema to see if this can be done anywhere.

Exclude ID numbers because we are already planning to switch to GUIDs for those in v12.

Possible to use hash-specific types on hash columns. For example, we could create a Composr type HASH_MD5 for MD5 hashes which translates to char(32) or binary(16). Or HASH_BCRYPT for CHAR(60) / BINARY(60). Or just HASH for our commonly-used 13-character hex hashes CHAR(13) / BINARY(7).
Steps to reproduce

Related to

#5546 - cms_stats table takes too much space
Funded? No
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated