cancel
Showing results for 
Search instead for 
Did you mean: 
Create a Post
Olga_Kuts
Silver

New measurements in Smart-1 datasheet

Hello!

Please explain in more detail the meaning of the measurements in Smart-1 datasheets: Sustained Logs Rate (Indexed), Peak Logs Rate (Indexed), Peak Logs Rate (Non-Indexed).

Thanks!

0 Kudos
2 Replies
Highlighted
Vladimir
Pearl

Re: New measurements in Smart-1 datasheet

If you are using SmartConsole to connect to each log server, as opposed to having a unified view of multiple sources in it, you can use a non-indexed logs:

Disabling Log Indexing

To save disk storage space, a Log Server can be configured to work in non-index mode. If you disable log indexing, queries will take longer. You must disable it on all management and Log Server objects in the environment. You are not allowed to have some Log Servers in index mode and other Log Servers in non-index mode.

When log indexing is disabled, you must connect with SmartConsole to each Log Server separately to query its logs. When you connect to the management server you do not get a unified view of all logs, as in index mode. On each Log Server, the search is done in one log file at a time.

0 Kudos

Re: New measurements in Smart-1 datasheet

As I understood it, from the Datasheet and from explanations of Dameon in New Smart-1 Appliances thread:

  • Sustained Logs Rate (Indexed) - Stable workload (24*7), no any problems. This is for how much they are really meant to be to be used. With log indexing enabled (SmartLog functions).
  • Peak Logs Rate (Indexed) - Maximum number of logs per second under heavy load (heavier than usual average). With log indexing enabled (SmartLog functions). This is measured for an hour. 
  • Peak Logs Rate (Non-Indexed) - Maximum number of logs per second under heavy load (heavier than usual average). With log indexing disabled. This is measured for an hour.

In addition, all of the log rate numbers published were obtained while the appliances exhibited good user experience.

Also log indexing takes a part of workload from SmartEvent servers, as it was discussed in other threads.