Skip to content

DB schema modernization, hot-rodding #35210

@wezell

Description

@wezell

Description

Now that we are postgres only, there a number of things we can do to help ourselves and improve dotCMS performance and remove tons of dead code.

This epic will be an overarching issue where we fix nasty db things like:

  • Remove non-postgres code paths
  • use postgres only features to improve performance
  • gently modify the the db schema to help us in a backwards compatible
  • Remove all our crazy select * from contentlet that returns 150 unneeded columns and only return the columns that are needed.
  • Unjoin tables like contentlet from inode
  • Use sparse indexes where values can be null
  • more to come

Desired Outcome

Improve dotCMS performance, remove old/unused code and code paths

Target Personas

  • Developer teams
  • Content teams
  • DevOps teams
  • System administrators (dotCMS)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status

    New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions