Is 30GB of RAM the max for this service?
Is 30GB of RAM the max for this service? That's rather paltry for very large joins, which seem plausible given they claim support to up to 64TB of data. Percona had recommended 144GB+ and moving to that from 64GB made our BI-type queries an order of magnitude faster. Obvi YMMV but in my experience one needs more RAM for joins before more disk for data. That said, the UI and system for managing replication looks pretty nice. I've never done MySQL admin directly but I do appreciate how much of a pain point this can be.
Posted by choppaface on Jul 28, 2015, 5:51 AM
Tags
Related issues
- It’s such an annoying problem to solve.
- > My point is, the impression many people will unavoidably take away from "many recalls" is that the vehicle must me in the shop all the ...
- [Feature]: Ability to merge old runs with a new run
- Add `findManyAndCount()` to return count of queried items
- One of the best, and first, things we did when starting our machine learning platform was to design it using a plugin architecture.
- gh pr push
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
ux (E-commerce)
It’s such an annoying problem to solve.
> My point is, the impression many people will unavoidably take away from "many recalls" is that the vehicle must me in the shop all the ...
[Feature]: Ability to merge old runs with a new run
Add `findManyAndCount()` to return count of queried items
One of the best, and first, things we did when starting our machine learning platform was to design it using a plugin architecture.
gh pr push
[feature]: Sync Collections with Git repo
Repeated SSH disconnects/reconnects that eventually stabilizes (large folder)
Is 30GB of RAM the max for this service?
Is 30GB of RAM the max for this service? That's rather paltry for very large joins, which seem plausible given they claim support to up to 64TB of data. Percona had recommended 144GB+ and moving to that from 64GB made our BI-type queries an order of magnitude faster. Obvi YMMV but in my experience one needs more RAM for joins before more disk for data. That said, the UI and system for managing replication looks pretty nice. I've never done MySQL admin directly but I do appreciate how much of a pain point this can be.
Comments (0)
No comments yet. Start the discussion.