From ba976732a990e49e377632c050314532219325cc Mon Sep 17 00:00:00 2001 From: Andriy Drozdyuk Date: Mon, 31 Jul 2017 00:05:47 -0400 Subject: [PATCH] Update README.md Fixed headings in the readme. --- README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index fbdabb4..3f11239 100644 --- a/README.md +++ b/README.md @@ -223,9 +223,9 @@ ok ``` --------- -##Scenarios and Corresponding Configuration Examples +## Scenarios and Corresponding Configuration Examples -####EXAMPLE 1: +#### EXAMPLE 1: * Add counter regulated queue called ___heavy_crunches___ to limit your cpu intensive code executions to no more than 7 at a time Configuration: @@ -250,7 +250,7 @@ jobs:run( heavy_crunches,fun()->my_cpu_intensive_calculation() end) ``` -####EXAMPLE 2: +#### EXAMPLE 2: * Add rate regulated queue called ___http_requests___ to ensure that your http server gets no more than 1000 requests per second. * Additionally, set the queue size to 10,000 (i.e. to control queue memory consumption) @@ -278,7 +278,7 @@ jobs:run(http_requests,fun()->handle_http_request() end) NOTE: with the config above, once 10,000 requests accumulates in the queue any incoming requests are dropped on the floor. -####EXAMPLE 3: +#### EXAMPLE 3: * HTTP requests will always have a reasonable execution time. No point in keeping them in the queue past the timeout. * Let's create ___patient_user_requests___ queue that will keep requests in the queue for up to 10 seconds @@ -310,7 +310,7 @@ we're likely to maximize the happy users! NOTE: In order to pace requests from both queues at 1000 per second, use __group_rate__ regulation (EXAMPLE 4) -####EXAMPLE 4: +#### EXAMPLE 4: * Rate regulate http requests from multiple queues Create __group_rates__ regulator called ___http_request_rate___ and assign it to both _impatient_user_requests_ and _patient_user_requests_ @@ -338,7 +338,7 @@ Create __group_rates__ regulator called ___http_request_rate___ and assign it t ``` -####EXAMPLE 5: +#### EXAMPLE 5: * Can't afford to drop http requests on the floor once max_size is reached? * Implement and use your own queue to persist those unfortunate http requests and serve them eventually @@ -378,11 +378,11 @@ Configuration: ``` -###The use of sampler framework +### The use of sampler framework 1. Get a sampler running and sending feedback to the jobs server. 2. Apply its feedback to a regulator limit. -####EXAMPLE 6: +#### EXAMPLE 6: * Adjust rate regulator limit on the fly based on the feedback from __jobs_sampler_cpu__ named ___cpu_feedback___ ```erlang