diff options
Diffstat (limited to 'src/latency.c')
| -rw-r--r-- | src/latency.c | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/src/latency.c b/src/latency.c index b5ccc7cc6..6148543c8 100644 --- a/src/latency.c +++ b/src/latency.c @@ -85,7 +85,7 @@ int THPGetAnonHugePagesSize(void) { /* ---------------------------- Latency API --------------------------------- */ /* Latency monitor initialization. We just need to create the dictionary - * of time series, each time serie is created on demand in order to avoid + * of time series, each time series is created on demand in order to avoid * having a fixed list to maintain. */ void latencyMonitorInit(void) { server.latency_events = dictCreate(&latencyTimeSeriesDictType,NULL); @@ -154,7 +154,7 @@ int latencyResetEvent(char *event_to_reset) { /* Analyze the samples available for a given event and return a structure * populate with different metrics, average, MAD, min, max, and so forth. - * Check latency.h definition of struct latenctStat for more info. + * Check latency.h definition of struct latencyStats for more info. * If the specified event has no elements the structure is populate with * zero values. */ void analyzeLatencyForEvent(char *event, struct latencyStats *ls) { @@ -343,7 +343,7 @@ sds createLatencyReport(void) { } if (!strcasecmp(event,"aof-fstat") || - !strcasecmp(event,"rdb-unlik-temp-file")) { + !strcasecmp(event,"rdb-unlink-temp-file")) { advise_disk_contention = 1; advise_local_disk = 1; advices += 2; @@ -396,7 +396,7 @@ sds createLatencyReport(void) { /* Better VM. */ report = sdscat(report,"\nI have a few advices for you:\n\n"); if (advise_better_vm) { - report = sdscat(report,"- If you are using a virtual machine, consider upgrading it with a faster one using an hypervisior that provides less latency during fork() calls. Xen is known to have poor fork() performance. Even in the context of the same VM provider, certain kinds of instances can execute fork faster than others.\n"); + report = sdscat(report,"- If you are using a virtual machine, consider upgrading it with a faster one using a hypervisior that provides less latency during fork() calls. Xen is known to have poor fork() performance. Even in the context of the same VM provider, certain kinds of instances can execute fork faster than others.\n"); } /* Slow log. */ @@ -416,7 +416,7 @@ sds createLatencyReport(void) { if (advise_scheduler) { report = sdscat(report,"- The system is slow to execute Redis code paths not containing system calls. This usually means the system does not provide Redis CPU time to run for long periods. You should try to:\n" " 1) Lower the system load.\n" - " 2) Use a computer / VM just for Redis if you are running other softawre in the same system.\n" + " 2) Use a computer / VM just for Redis if you are running other software in the same system.\n" " 3) Check if you have a \"noisy neighbour\" problem.\n" " 4) Check with 'redis-cli --intrinsic-latency 100' what is the intrinsic latency in your system.\n" " 5) Check if the problem is allocator-related by recompiling Redis with MALLOC=libc, if you are using Jemalloc. However this may create fragmentation problems.\n"); @@ -432,7 +432,7 @@ sds createLatencyReport(void) { } if (advise_data_writeback) { - report = sdscat(report,"- Mounting ext3/4 filesystems with data=writeback can provide a performance boost compared to data=ordered, however this mode of operation provides less guarantees, and sometimes it can happen that after a hard crash the AOF file will have an half-written command at the end and will require to be repaired before Redis restarts.\n"); + report = sdscat(report,"- Mounting ext3/4 filesystems with data=writeback can provide a performance boost compared to data=ordered, however this mode of operation provides less guarantees, and sometimes it can happen that after a hard crash the AOF file will have a half-written command at the end and will require to be repaired before Redis restarts.\n"); } if (advise_disk_contention) { |