ES stream writing slow...

Hi Team,

  I am having trouble with Event Store. I have version ES version 2.0 single Node, running on Windows 2012 R2 Standard 4

GB RAM, 64 bit OS. It is PROD box
ES Log shows " [PID:03836:032
2016.05.12 03:17:10.349 TRACE QueuedHandlerThreadP] SLOW QUEUE MSG [StorageReaderQueue #3]: ReadStreamEventsForward - 1140ms. Q: 0/3."
Does this mean that it will have slowness in writing to the stream and returning back the result…
Please help me out. My application is very when writing to the ES.
Any documentation or link also will be very helpful.
Thanks

This message is saying it had a slow read from disk (that took
1140ms). This is not involved with writing.

"My application is very when writing to the ES." I think there is a
word missing in this sentence (after very?)

I meant “My application is very when writing to the ES” each command is taking around 1 to append to stream… Is the system requirement fine on my server?

I meant “My application is very when writing to the ES” each command is taking around 1 to append to stream… Is the system requirement fine on my server?

Regards

Very slow when writing?

Is the system requirement fine on my server?

The main thing about writing is what the disk is.

Not sure if it is only writing or reading or both… Attaching log file…

Regards

10.255.1.35-2113-single-node.log (421 KB)

Most of these are on reads. The single largest thing controlling this
is what type of disk you have.

Hi Greg,

This is what we are using.
“FC SAN DotHill (DH3930)”

Regards
Himanshu Chandra

A SAN is commonly slower than a locally attached disk. Is there a
performance problem that you are observing? or are you just worried
about the messages?

Hi Greg,

Messages are going fine and have no issues but it so slow that it is taking approx 1 minute each command to commit to Event Store.

Regards
Himanshu Chandra

How are you measuring this? Writing is usually very fast. 1 minute is
very ridiculous.

Hi

So we have a application that pushes command to the event store. Now we go to the event store interface and see that each command is taking 1 minute. Attaching is the screen shot.

Regards
Himanshu Chandra

Capture.PNG

This doesn't sound like an accurate measurement. Just because only one
command is written every one minute does not imply that event store is
taking one minute per command to write.

If you time the append operation in code how long does it take?

The slow warnings in your logs were on reads and were mostly a few
hundred milliseconds (nowhere near minutes)

But the same code is working fine on Dev machine. Streams are append in a second.

Regards