Nature of elastic search - CPU bound, IO bound or network bound

I want to know the nature of elastic search database, in the case when I am
shipping logs via an indexer from redis to the ES database.

I have to figure out the types of each of these - Redis, Indexer(which I
know is CPU bound), and ES so that I can determine which system to run
which one on.

Please help.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

In short all of the above... well ES is a search engine rather than a
database while the transitions between those vanish over time I guess. For
indexing CPU and IO might be saturated if you can ship docs quick enough.
It also depends on the documents (size and complexity for indexing)
Networking internally should not be near the CPU usage but present. For
Searching its also IO and CPU that is used intensively while CPU is most
prominent here.

hope that helps a bit further

simon

On Monday, May 20, 2013 6:01:56 AM UTC+2, Aakash Anuj wrote:

I want to know the nature of elastic search database, in the case when I
am shipping logs via an indexer from redis to the ES database.

I have to figure out the types of each of these - Redis, Indexer(which I
know is CPU bound), and ES so that I can determine which system to run
which one on.

Please help.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.