Skip to:
Current issue:
Slowness can be noticed while running pbm status or pbm status -s backups on environments with large datasets and many backups.
How to reproduce:
1 . Deploy MongoDB with a reasonable data set, in this case ~8GB. **
2. Take a logical backup.
3. Enable PITR.
4. Create some basic workload to have the oplog moving and increase PITR size.
5. Start taking backups
After a few backups, we start to see a performance degradation on the pbm status.
That number may vary:
But that's definitely slower than using pbm list.
Which may also vary, but nothing close as seem on pbm status.
Current issue:
Slowness can be noticed while running pbm status or pbm status -s backups on environments with large datasets and many backups.
How to reproduce:
1 . Deploy MongoDB with a reasonable data set, in this case ~8GB. **
2. Take a logical backup.
3. Enable PITR.
4. Create some basic workload to have the oplog moving and increase PITR size.
5. Start taking backups
After a few backups, we start to see a performance degradation on the pbm status.
That number may vary:
But that's definitely slower than using pbm list.
Which may also vary, but nothing close as seem on pbm status.