[DOCS-2866] Document that --auditFormat JSON is slower than --auditFormat BSON Created: 07/Mar/14  Updated: 11/Jan/17  Resolved: 10/Mar/14

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Davide Italiano Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

$ uname -a
Linux localhost.localdomain 3.12.10-300.fc20.x86_64 #1 SMP Thu Feb 6 22:11:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux


Attachments: PNG File audit.png    
Issue Links:
Related
Participants:
Days since reply: 9 years, 49 weeks, 2 days ago

 Description   

While audit introduces a non-trivial overhead on any workload (reads become writes), different formats used have different impact.
In my tests – audit with --auditFormat BSON introduces 2x slowdown on a read-only workload, while --auditForrmat JSON introduces a 4x slowdown (see attached screenshot).
This is kind of expected, since translating BSON into JSON is not all that efficient, but this should be documented.



 Comments   
Comment by Githook User [ 10/Mar/14 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2866 audit to JSON file slower than BSON file
Branch: master
https://github.com/mongodb/docs/commit/2e111a8b309ddef46cb93928e305a757c24eaef3

Generated at Thu Feb 08 07:44:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.