Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Redis DB
Home
+ new post
About this group
Join this group
Message from discussion How to measure fork() time on bgrewriteaof?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Alexander Gladysh  
View profile  
 More options Oct 14 2012, 6:23 am
From: Alexander Gladysh <aglad...@gmail.com>
Date: Sun, 14 Oct 2012 14:22:34 +0400
Local: Sun, Oct 14 2012 6:22 am
Subject: Re: How to measure fork() time on bgrewriteaof?
Print | View thread | Show original | Report this message | Find messages by this author

On Sun, Oct 14, 2012 at 1:39 PM, Alexander Gladysh <aglad...@gmail.com> wrote:
> On Sun, Oct 14, 2012 at 1:25 PM, Salvatore Sanfilippo <anti...@gmail.com> wrote:
>> On Sun, Oct 14, 2012 at 11:22 AM, Alexander Gladysh <aglad...@gmail.com> wrote:

>>> That is 0.0001s, right? This means that fork is not a problem in my setup...

>> No it is 0.1 seconds, so 100 milliseconds, still not a big deal
>> depending on your latency requirements.

> Well, that's more or less bearable. So, 10 seconds for BGREWRITEAOF
> here is probably HDD after all... (weird, dataset is about a
> gigabyte...)

> [755] 14 Oct 12:27:57 * Background append only file rewriting started
> by pid 21552
> [755] 14 Oct 12:28:01 * Asynchronous AOF fsync is taking too long
> (disk is busy?). Writing the AOF buffer without waiting for fsync to
> complete, this may slow down Redis.
> [755] 14 Oct 12:28:03 * Asynchronous AOF fsync is taking too long
> (disk is busy?). Writing the AOF buffer without waiting for fsync to
> complete, this may slow down Redis.
> [755] 14 Oct 12:28:06 * Asynchronous AOF fsync is taking too long
> (disk is busy?). Writing the AOF buffer without waiting for fsync to
> complete, this may slow down Redis.
> [21552] 14 Oct 12:28:07 * SYNC append only file rewrite performed
> [755] 14 Oct 12:28:07 * Background AOF rewrite terminated with success
> [755] 14 Oct 12:28:07 * Parent diff successfully flushed to the
> rewritten AOF (436762 bytes)
> [755] 14 Oct 12:28:07 * Background AOF rewrite successful

BTW, is there a way to conclusively *prove* that this is due to HDD? I
see consistently 7-10 seconds per rewrite.

I already asked something along these lines recently here, but there
were no *concrete* answers (or I missed them). Sorry for lazyish
question, answers "read my post [link] again and do your homework" are
accepted (but if someone can give specifics, it will be much
appreciated).

Thanks,
Alexander.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google