Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

2017-10-23 Thread Viktor Klang
What definition of latency are you using? (i.e. how is it derived) On Mon, Oct 23, 2017 at 10:11 PM, Gary Malouf wrote: > Hi Konrad, > > Our real issue is that we can not reproduce the results. The web server > we are having latency issues with is under peak load of

Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

2017-10-23 Thread Viktor Klang
No, I mean, is it from first-byte-received to last-byte-sent or what? On Mon, Oct 23, 2017 at 10:22 PM, Gary Malouf wrote: > We are using percentiles computed via Kamon 0.6.8. In a very low request > rate environment like this, it takes roughly 1 super slow

Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

2017-10-23 Thread Gary Malouf
Yes, it gets parsed using entity(as[]) with spray-json support. Under a load test of say 1000 requests/second these latencies are not visible in the percentiles - they are easy to see because this web server is getting 10-20 requests/second currently. Trying to brainstorm if a dispatcher needed

Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

2017-10-23 Thread Gary Malouf
Hi Konrad, Our real issue is that we can not reproduce the results. The web server we are having latency issues with is under peak load of 10-15 requests/second - obviously not much to deal with. When we use load tests (https://github.com/apigee/apib), it's easy for us to throw a few

Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

2017-10-23 Thread Gary Malouf
We are using percentiles computed via Kamon 0.6.8. In a very low request rate environment like this, it takes roughly 1 super slow request/second to throw off the percentiles (which is what I think is happening). On Mon, Oct 23, 2017 at 4:20 PM, Viktor Klang wrote: >

Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

2017-10-23 Thread Gary Malouf
It is from when I start the Kamon trace (just inside of my path("myawesomepath") declaration until (theoretically) a 'complete' call is made. path("myawesomepath") { traceName("CoolStory") { ///do some stuff complete("This is great") } } For what it's worth, this route is a 'POST' call. On

Re: [akka-user] No shutDown on Materializer

2017-10-23 Thread Konrad “ktoso” Malawski
Hi Richard, Saying that “using Materializer” will cause leaks is somewhat of a weird phrasing, since that sounds just like “using ActorSystem can cause leaks” — well sure, just like “using objects can cause leaks” :-) Let’s step back and analyse where your colleague’s statement came from, and

Re: [akka-user] No shutDown on Materializer

2017-10-23 Thread Richard Rodseth
Hi Konrad. I don't believe I used that phrase, but thanks for elaborating. I will digest what you wrote and discuss it. Any thoughts on having a lifecycle method on Materializer vs ActorMaterializer? On Mon, Oct 23, 2017 at 7:39 PM, Konrad “ktoso” Malawski < konrad.malaw...@lightbend.com> wrote:

Re: [akka-user] No shutDown on Materializer

2017-10-23 Thread Richard Rodseth
Here you go https://github.com/akka/akka/issues/23837 On Mon, Oct 23, 2017 at 10:22 PM, Konrad “ktoso” Malawski < konrad.malaw...@lightbend.com> wrote: > Adding the shutdown method to the interface you mean? > I guess it could be considered, please open a ticket. > Technically it would be

Re: [akka-user] No shutDown on Materializer

2017-10-23 Thread Konrad “ktoso” Malawski
Adding the shutdown method to the interface you mean? I guess it could be considered, please open a ticket. Technically it would be breaking to do so, but materializers are somewhat special “internal” one might say. -- Cheers, Konrad 'ktoso ' Malawski Akka @

[akka-user] Akka TCP and Slow Start Restart

2017-10-23 Thread Alan McSherry
One of the building blocks of TCP is "slow start" and "slow start restart" https://hpbn.co/building-blocks-of-tcp/#slow-start In particular for bursty applications "slow start restart" could be hampering the performance of an Akka app by not using the full bandwidth available at the time

Re: [akka-user] Re: Error handling with Source.queue BroadcastHub

2017-10-23 Thread Andrew
Perhaps, but I think that would be really tedious to implement in a real-life implementation, because it's not just one aspect of the graph that can fail. I'd have to construct a lot of different failed types to float downstream and handle failures at each junction of the graph. In cases where I'm

[akka-user] [akka-http] Hosting an akka-http app in Google Compute VM

2017-10-23 Thread Samik R
I am trying to host an app built using akka-http, which serves as a REST API backend, on a Google Compute VM. Things work fine, but seem a bit slow: each request roundtrip takes ~5 seconds. Few things I have realized I am doing: - I have chosen the lowest of the VM configs for now, for testing

[akka-user] Re: Error handling with Source.queue BroadcastHub

2017-10-23 Thread Tim Harper
Have you considered wrapping your erroneous request in a Try ? val (queue: SourceQueueWithComplete[String], source: Source[String, NotUsed]) = sourceQueue .via(Flow[String].map { num => println(s"flow handling ${num}") if (num == "1") { Failure(new