Skip to content

fix(velocity): Memory and sync issues #34046

@wezell

Description

@wezell

Problem Statement

There are a number of improvements we can make to velocity to improve its memory footprint. For starters, we do not even stream our responses, we turn them into String buffers and then send them.

Additionally, there are a number of places where we can use ThreadLocals to store buffers and arrays and not have to reallocate them on every page hit.

Also would like to get rid of the synchronized block in the DotResourceLoader that we have seen act up.

  • Retain full backward compatibility
  • Ensure all tests pass
  • Benchmark the code before and after

dotCMS Version

latest

Conversation link

https://dotcms.slack.com/archives/C04FRV45YR5/p1765222245235399

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Status

    New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions