Document and run benchmarking

[utkarsharma2]

Please describe the feature you'd like to see

1. Document the config.json
2. All the esoteric features
3. @pankajastro should be able to run benchmarking without any support

Describe the solution you'd like
A clear and concise description of what you want to happen, if possible with code examples.

Are there any alternatives to this feature?
Is there another way we could solve this problem or enable this use-case?

Additional context
Add any other context about the feature request here.

Acceptance Criteria

• All checks and tests in the CI should pass
• Unit tests (90% code coverage or more, once available)
• Integration tests (if the feature relates to a new database or external service)
• Example DAG
• Docstrings in reStructuredText for each of methods, classes, functions and module-level attributes (including Example DAG on how it should be used)
• Exception handling in case of errors
• Logging (are we exposing useful information to the user? e.g. source and destination)
• Improve the documentation (README, Sphinx, and any other relevant)
• How to use Guide for the feature (example)

[pankajastro]

I have tried to document it here https://docs.google.com/document/d/1ZW4IkwqMTOKmDYD6unrFb3-Ii49X35MEwLpcPQuhzhU/edit?usp=sharing

[sunank200]

Closing this as documentation is completed from @pankajastro .