• 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle





  • BlueBockser@programming.devtoProgrammer Humor@programming.devSee MongoDB
    link
    fedilink
    arrow-up
    11
    arrow-down
    4
    ·
    edit-2
    2 months ago

    What’s the problem with that? In my previous team, we had a structure with four levels of nesting where we only ever needed to query the first two levels. At first we used Postgres with normalized tables, but it was just slow as hell. Switching to MongoDB actually made our performance issues vanish.

    Of course it all depends on what kinds of queries you need to run, but I don’t think that large JSON documents are necessarily a problem.












  • You still have 63% RAM available in that screenshot, there are zero problems with Java using 13% RAM. It’s the same as the tired old trope of “ChRoMe Is EaTiNg My MeMoRy”. Unused memory is wasted memory if it can be used for caching instead, so unless you’re running out of available memory, there is no problem.

    Also, the JVM has a lot of options for configuring its various caches as well as when it allocates or releases memory. Maybe take a look at that first.

    Edit: Apparently people don’t want to hear this but don’t have any actual arguments to reply with. Sorry to ruin your “JaVa BaD” party.