[SERVER-48548] Create a Performance Test for Auditing with Sharding / Replication Created: 02/Jun/20 Updated: 29/Oct/23 Resolved: 23/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Salman Baset | Assignee: | Sara Golemon |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2020-11-16, Security 2020-11-30, Security 2020-12-14, Security 2020-12-28 | ||||
| Participants: | |||||
| Description |
|
Users interested in enabling auditing often ask "what is the performance hit of enabling various types of auditing in the Server". Specifically, if they enable write/update only auditing or ready only auditing or both, how should they setup the cluster topology. Of course, the auditing performance also depends on the users' workload, but the users are also interested in understanding some ball park numbers. Thus, it would be helpful to have a test where YCSB workloads are run against the following configurations: |
| Comments |
| Comment by Githook User [ 23/Dec/20 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: |