Hi,
I'd just like to share my satisfaction from Akka HTTP performance in 2.4.10.
I'm diagnosing some low level Node.js performance issues and while running
various tests that only require the most basic "Hello World" style code, I
decided to take a few minutes to check how would Akka HTTP
Thanks!
Adding -k indeed fixes this right away:
ab -k -c 400 -n 10 -m GET http://127.0.0.1:3000/
This is ApacheBench, Version 2.3 <$Revision: 1706008 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apac
-m GET http://127.0.0.1:3000/
This is ApacheBench, Version 2.3 <$Revision: 1706008 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking 127.0.0.1 (be patient)
Completed 1 requests
Complete
llo(final String name, final int
times) {
...
On Monday, September 5, 2016 at 5:28:19 PM UTC+3, Adam wrote:
>
> Hi,
>
> I'm looking at the docs trying to find an example of how to create a route
> that does not complete the result synchronously from the route tree, but
&
to do.
Adam.
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>
cond for the fastest requests.
On Tuesday, April 19, 2016 at 12:25:24 AM UTC+3, Adam wrote:
>
> Yeah, no code is rather silly really...
>
> I've created this repository:
>
> https://github.com/adamhonen/Akka-Http-performance-test
>
> I didn't get a chance to try the s
s a new connection with
>>> the current akka-http version is to disable autoFusing (which is pretty
>>> costly). That can be done when you create the materializer like this:
>>>
>>>
>>> ActorMaterializer(ActorMaterializerSettings(system).withAutoFusing(false))
>>>
OK, thanks.
So just to be certain - in the meantime, is it expected that I'll see Akka HTTP
perform ~100 times worse (or let's just say "much worse") than Play framework
for such cases?
I was hoping it's actually something that I'm doing wrong because I was
expecting it to be worse per the
Hi,
I see Rejections are only described in the Scala version of the docs.
Is that on purpose?
What are my options using the Java API in order to customize rejections?
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>>
p; map(_ + 1),
> second the map(_ * 2) & sink?
>
>
> Again correct :-) Would you mind if I just used this example in the docs?
>
Sure, no problem :)
Thanks again!
Adam
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>&g
(different name?) which stages will run concurrently by default?
Thanks,
Adam
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/c
/after it.
> 4. which built-in stages are fuseable by default? The docs are quite vague
> here saying only "linear" ones. Which ones are these?
>
>
> It is easier to name the exceptions: SslTlsStage, groupBy, and some
> sources and sinks (but for those the differenc
guide-1.0-2.x-scala.html,
linked from the blog.
This says that:
"Fusable elements are
* all GraphStages (this includes all built-in junctions apart from groupBy)
* all Stages (this includes all built-in linear operators)"
though I'm not sure which elements are linear, stages or grap
not that much work anyway.
Thanks!
On Monday, December 14, 2015 at 10:53:13 AM UTC+2, Johan Andrén wrote:
>
> Hi Adam,
>
> I think what you are describing is covered in the logging docs:
> http://doc.akka.io/docs/akka/2.4.1/scala/logging.html#Loggers and
> http://doc.akka.io/do
Hi,
I sometimes see this issue where I want to switch logs to DEBUG, but due to
the large number of messages the JVM will crash on OutOfMemory which turns
out to be due to the accumulation of logging events.
Most logging frameworks have the ability to drop messages beyond a certain
number and
Hello,
now I better understand queries like allPersistenceIds() and
eventsByPersistenceId(persistenceId). What can I do if persistent query
implementation I use does not support live stream of events? Should I
implement polling myself (schedule message to self and after receive call
query
But that is not really accurate, isn't it?
When restarted the ActorRef is still perfectly valid and you only need to watch
actors in case you have reason to believe that they will be terminated. Also,
messages don't get lost during the restart, because the mailbox isn't restarted
(well
remill/akka-http-session) which contains some
basic support for JWT - sessions can be now transported using headers
(instead of cookies), and encoded in the specified json-based format.
Adam
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>&
Hello,
recently I read through new akka-persistence-query-experimental module and
would like to see some tutorials and examples to see how it can work.
Documentation is really abstract for me. Unfortunately, I'm not able to
find any activator templates nor tutorials.
What I understand is how
adding an additional inlet to the actor. That leads
> to many problems, shared mutable state and multithreading inside the actor
> to name just two. I may be wrong. Maybe Patrik can comment on that.
>
>
> Mike
>
>
>
> On Tuesday, October 20, 2015 at 8:32:50 AM UTC+2,
Hi,
In my system I have an initialization sequence that must take place at a
certain order.
Basically I don't want to open my system for incoming requests, before all
services are properly started.
So what I needed is sort of similar to what you describe here.
I've implemented it without ask.
But thank you for your thoughts.
Dne úterý 20. října 2015 10:41:32 UTC+2 Patrik Nordwall napsal(a):
>
>
>
> On Tue, Oct 20, 2015 at 8:26 AM, Adam Dohnal <dohna...@gmail.com
> > wrote:
>
>> You understand it right. Unfortunately, your solution won't work. Suppose
>> p
asyncrounous player.observable.subscribe callback. Since this is an actor
> you must turn that callback into a message that is sent to self and when
> receiving that message you can persist it.
>
> /Patrik
>
> On Mon, Oct 12, 2015 at 3:17 PM, Adam Dohnal <dohna...@gmail.com
> > wrote:
&g
I don't understand the purpose of "keeping the actor busy".
Why not use the actor system's scheduler in order to implement the delay?
Do you actually want to use CPU or other resources?
The only thing to pay attention to is that the scheduler, has a certain
precision, so the delay may turn out
, which is already not trivial (at least in my eyes as compare it to
RxJava\RxScala).
Usually having less options can make things simpler, but in this case I
know I’ve used the addEdge method in order to try and make sense of how to
use the Akka streams DSL.
Adam
On Saturday, October 17, 2015
Hello,
I am new in Akka and I am trying to develop some mini project to test some
things (akka, rx, cqrs, es etc..)
I think I understand the concept of cqrs/es and how it fit to akka. My
problem is probably more theoretical than technical.
Let's say, I have class Player, which has several
Hi,
I've been looking for a way to create a client that upon disconnection will
try to reconnect.
I've done this in the past with RxJava observables, but I'm not sure how to
do this using Akka Streams.
I saw some code examples where PushStage is being used to implement this,
but the code
You can easily check what Roland suggested.
1. Setup the frequency of the scheduling to be very fast so memory will
grow quickly.
2. connect with visualvm\jconsole to the jvm and initiate gc manually.
3. Compare the trend of memory of the moments right *after the GC* and
see if
What kind of web container (if any are you using)?
I'd say using ask and blocking on it is still an improvement with pre 3.0
servlets.
With asynchronous servlets you can push the AsyncContext down in a message or
use as in the ask future's onComplete callback.
With other frameworks (Netty,
https://gist.github.com/adamhonen/8863088641df095cce96
Here, I hope that helps.
On Tuesday, August 25, 2015 at 11:52:18 AM UTC+3, Dennis Jönsson wrote:
Den måndag 24 augusti 2015 kl. 18:58:26 UTC+2 skrev Adam:
I've worked around this by starting an actor that polls a regular slf4j
logger
I've worked around this by starting an actor that polls a regular slf4j logger
and then changes the akka log level at run time through the event bus.
It works well enough, although it means selective log levels still incur a high
overhead, regardless of logging frequency and it also means that
://groups.google.com/d/optout.
--
Adam Shannon | Software Engineer | Banno | Jack Henry
206 6th Ave Suite 1020 | Des Moines, IA 50309 | Cell: 515.867.8337
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives
is the relation with the blog post?
El lunes, 24 de agosto de 2015, 19:13:00 (UTC+1), Adam Shannon escribió:
I thought there were plans for akka-stream to move away from actors as
the implementation detail. Is that still the case?
On Mon, Aug 24, 2015 at 1:07 PM, Gabriel Volpe volpeg
.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
--
Adam Shannon | Software Engineer | Banno | Jack Henry
206 6th Ave Suite 1020 | Des Moines, IA 50309 | Cell: 515.867.8337
--
Read the docs: http://akka.io/docs
The general answer similar questions usually get here is that you'll have to
measure, but here are a few comments:
1. I'd check what's causing these spikes. The usual suspect is GC.
2. You didn't mention what handling such a request means. Optimally with 2
cores you have 2000ms per second worth
Hey all,
We've been working on integrating some codahale metrics into akka-http.
This has been heavily by the spray PR[0], but ported over to the akka-http
classes.
https://github.com/Backline/akka-http-metrics
We're running this in production for a little while now and would love it
if
you'd be impacted
by this, because nginx seems to be properly handling these requests.
On Mon, Jul 20, 2015 at 4:21 AM, Viktor Klang viktor.kl...@gmail.com
wrote:
Hi Adam,
What should it do instead of throwing the exception?
(In case it is legal according to the HTTP spec please point
is what akka-http is doing
with no Host header present. (I'd need to fork some well-conforming library
and break it.)
On Mon, Jul 20, 2015 at 8:15 AM, Viktor Klang viktor.kl...@gmail.com
wrote:
Adam,
you'd like Akka Http to respond with a 400 in case Host is omitted?
What does the spec mandate
to
#17992?
Yes, it seems both you and Adam suffered from #18044 which means that
HTTP/1.0 requests without a Host header failed noisily. But you were
probably additionally affected by #17992 which (dependently of #18044
or not) unbound the server for some error conditions.
Johannes
Johannes,
Yes, that seems to be the only issue left that I have. I'm not sure if
Nicolau is having any other issues.
On Mon, Jul 20, 2015 at 8:33 AM, 'Johannes Rudolph' via Akka User List
akka-user@googlegroups.com wrote:
Hi Adam,
On Mon, Jul 20, 2015 at 3:25 PM, Adam Shannon adam.shan
-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
--
Adam Shannon | Software Engineer | Banno | Jack Henry
206 6th Ave Suite 1020 | Des Moines, IA 50309 | Cell: 515.867.8337
--
Read the docs
PM, Viktor Klang viktor.kl...@gmail.com
wrote:
Adam,
thank you. Are you observing any undesired behavior from Akka Http related
to those requests?
On Sun, Jul 19, 2015 at 10:43 PM, Adam Shannon adam.shan...@banno.com
wrote:
I have some logs of this happening to me as well. I'm running
Looks like there's something for spray:
http://github.com/gettyimages/spray-swagger
I imagine there's nothing for Akka HTTP, seeing as it's not even officially
released yet.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
to create a GH
issue if you think that would be a good idea :)
Adam
Good luck going forwards! Libraries like these are very useful.
/Magnus
Den fredag 10 juli 2015 kl. 16:41:17 UTC+2 skrev Adam Warski:
Hello,
I started recently working on a small side-project containing akka-http
directives
in
(automatically or manually).
Thanks,
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google
The project is just over a week old, so code reviews / comments / etc. more
than welcome :)
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You
scala -cp your jar
On Monday, June 29, 2015 at 11:58:14 AM UTC+3, john@gmail.com wrote:
Sorry that I know so little about scala.
I have written a java akka system which uses maven for dependeny
management.
I would now like to inspect my configuration (Typesafe Config Library
There’s actually one thing you need to take into account when using
DynamoDB for persistence.
I've been bitten by this a few times when using other Amazon services.
The Java SDK provided by Amazon includes two interfaces: synchronous and
asynchronous.
I imagine you’d prefer to use the
On Sat, Jun 13, 2015 at 8:11 PM, Sebastian M Cheung
minsche...@googlemail.com wrote:
Hi Adam,
I just saw your post, and I am also keen on building more Scala based
Android apps but I couldn't find any good tutorials.
So from your experience it was worth the effort that you managed to use
/outlet).
Ah! Now I have:
class SplitRoute[T](splitFn: T = Either[T, T]) extends FlexiRoute[T,
UniformFanOutShape[T, T]](
new UniformFanOutShape(2), OperationAttributes.name(SplitRoute)) { ... }
and I can use the nicer DSL.
Thanks,
Adam
--
Read the docs: http://akka.io/docs
You can take 2 heap dumps a day or more apart and then use Eclipse MAT to
compare them (there's a compare basket feature that is very useful in such
cases).
Actually there's a good chance that even a single heap dump will suffice if the
JVM has been running for long enough. Try to use the leak
options, visit https://groups.google.com/d/optout.
--
Adam Shannon | Software Engineer | Banno | Jack Henry
206 6th Ave Suite 1020 | Des Moines, IA 50309 | Cell: 515.867.8337
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional
this is so, but when I have a
Merge, I can just do:
in ~ merge ~ out
But when I have a FlexiMerge, I need to do:
in ~ flexiMerge.in0
flexiMerge.out ~ out
it seems Merge's shape is also an Inlet, but I can't find that in the code
:)
--
Thanks,
Adam
--
Read the docs: http
Hi,
Where I work, we're using Akka with log4j2 (through slf4j binding) in
production.
We're handling billions of daily requests and so far it works flawlessly :-)
On Thursday, May 21, 2015 at 10:55:22 AM UTC+3, monika singhal wrote:
Anyone tried log4j2 with Akka ?
Thanks,
Monika
--
Unhandled is mainly useful for troubleshooting. Akka won't check if you
actually did something with the message or not. It also doesn't force you to
call unhandled and probably (never tried this) does't prevent you from calling
unhandled multiple times. The documentation goes into detail
First of all, regardless of inclusion, you need your build to exclude this
application.conf file from jars. There's not much point for a configuration
file that can't be easily modified. It should instead be in a folder (e.g.
./conf) that is added to your classpath.
Then, you can either add
Hi,
First of all, actors are very lightweight and you can have many of them, while
an ActorSystem is heavyweight and you should not have many of that (typically
you'd have one).
As for the pattern you describe - it all depends on the fine details, but if I
had to implement a service that
not complete
during the time defined in timeoutDuration, then it will throw A
TimeoutException.
-Endre
On Thu, Apr 9, 2015 at 1:27 PM, Adam Daines daine...@gmail.com
javascript: wrote:
Hi all,
I've got a question in relation to the unit testing of a piece of non
actor code that produces
Hi all,
I've got a question in relation to the unit testing of a piece of non actor
code that produces a FutureActorRef via performing an
actorSelection().resolveOne on the ActorSystem.
Within the Future.onFailure() a value is being set that I would like to
test but the Future is making use
would be much appreciated.
Thanks.
On Thursday, April 9, 2015 at 1:46:22 PM UTC+1, Adam Daines wrote:
Thank you both for the quick and helpful responses!
Our issue is now resolved :)
Thanks.
On Thursday, April 9, 2015 at 1:01:24 PM UTC+1, √ wrote:
Ouch, nice catch, now we've covered
First of all, you shouldn't ever block like this, as you do with Await.
As for your question - this sounds like something the parent actor should
be responsible for.
I'm not even sure the code above works (it at least never occurred to me to
try to create an actor using a full path as I always
Thx a lot for the amazing work
Already used by beta feature at Clever Cloud ;-)
Best Regards,
Le vendredi 27 février 2015 17:08:24 UTC+1, rkuhn a écrit :
Dear hakkers,
we are pleased to announce the availability of the fourth milestone of
Akka Streams HTTP. The biggest directly visible
Hello,
I would like to ask if anyone from Akka Team would like to be Google Summer
of Code mentor this year?
Cheers,
Adam Kozuch
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https
I'll refer you to here: http://doc.akka.io/docs/akka/2.3.9/dev/io-layer.html
It says Akka IO is designed with the requirement of scalability to millions of
concurrent connections.
Of course, this typically requires tuning (including at the OS level), but
sounds like 50k should be supported. I
I believe 50M messages per second on a single machine was mainly an example
for scaling up. See the kind of machine that was used for it
http://letitcrash.com/post/20397701710/50-million-messages-per-second-on-a-single
.
Anyway, have you tried doing the same analysis on the legacy driver?
It
I think the OS you're using matters a lot for this sort of test. Hopefully
it's not windows...
What was the maximum concurrency level that you've tested?
Did you make sure (in the performance test code) that this concurrency
level is actually met in all cases?
Did you try tweaking with the
down to that same point. Is this the plan going forward, or perhaps is
there some other strategy that will be used?
[0]: https://groups.google.com/forum/#!topic/spray-user/avYhEFYsvcg
--
Adam Shannon | Software Engineer | Banno | Jack Henry
206 6th Ave Suite 1020 | Des Moines, IA 50309 | Cell
So why not always return OK in such cases?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed
}
@Override
public UntypedActor getActor() {
return this;
}
}
Finally, for asynchronous paths we simply use more actors, but I assume
that was already obvious to you and you were asking about the previous part
of my answer.
I hope this helps.
Adam.
On Tuesday, January
to work on the issue, I assume master
is a good starting point?
Adam
On Friday, January 2, 2015 3:58:37 PM UTC+1, Patrik Nordwall wrote:
Hi Adam,
We have been thinking that this should be handled with a smarter downing
strategy, but since it would be easy to implement it in the singleton
Ok, if there's only one ball, that answers the question. Thanks! :)
Adam
On Thursday, January 1, 2015 10:00:27 AM UTC+1, Akka Team wrote:
Hi Adam,
PushPull stage callbacks are never concurrent. Also, if a stage calls
ctx.Push then it will receive eventually an onPull, and whenever it calls
), the singleton starts up anyway).
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed
Done, issue added: https://github.com/akka/akka/issues/16547
Adam
On Monday, December 15, 2014 12:16:17 PM UTC+1, Björn Antonsson wrote:
Hi Adam,
Yes, that seems to bit awkward. And yes that part of the TCP API also
feels a bit backwards. I think that we need to revisit these things when
? :)
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups Akka
User List
Seems I forgot to actually write the title, sorry ;) It should be sth like
No-element never-completed source
Adam
On Thursday, December 11, 2014 11:33:42 AM UTC+1, Adam Warski wrote:
Hello,
I'm migrating to the latest streams, the new client-server stream tcp flow
does require some mind
Try running mvn dependency:tree (before and after commenting out).
It will show you exactly how you get each library.
Most probably you're getting akka 2.3.X for scala 2.11 as a transitive
dependency.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
if you could tinker around it.
Random fact is that Kafka is *so much used everywhere* that it definitely
would find users/contributors I think :-)
great, always good to validate ideas :)
thanks,
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs
is implemented as described here:
http://doc.akka.io/docs/akka/2.3.7/scala/io-tcp.html (with propagation to
the writer side by using TCP buffers), right? If the subscriber doesn't
generate demand, this will result in suspending reading from the socket?
Adam
--
Read the docs: http
I opened GH issues and I see Konrad beat me to
it: https://github.com/akka/akka/issues/16348 :)
Adam
On Wednesday, November 19, 2014 8:36:41 AM UTC+2, rkuhn wrote:
Hi Adam,
your initial point of creating a growing (and maybe thundering) herd of
retries is a good one and it would be better
It's a matter if opinion and I risk stating the obvious, but my (unoriginal)
rules of thumb are:
Updates to internal state are out of scope for tests. Sometimes when something
is not testable, it's for a good reason - you're code should simply be
modified. This is one of those cases.
Adding
-actors.
Thanks!
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups Akka
with this is somehow wrong? :)
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups
I suspect a thread dump in this state and the akka version you're using would
be invaluable to understanding this.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
On Thu, Oct 30, 2014 at 1:43 PM, Adam Warski ad...@warski.org
javascript: wrote:
There's an OnCompleteDrain :) (btw. - sink, drain, subscriber - a lot of
names ;) )
Drain is no longer there (as a name at least) and you should usually not
see a Subscriber ;)
It is in 0.9, but as I
creating the specific
Subscriber, here it's implemented by the TCP extension? E.g. a Future or
similar as part of the binding: StreamTcp.OutgoingTcpConnection?
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
is certainly nice. Though the fact that a socket died doesn't
always require protocol support (I mean, often you will know that a socket
isn't working without sending special pings or such). So this could get
exposed to the user.
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ
Sure :) I'm using streams 0.9, scaladsl2 and I want to add failure
detection to that:
https://github.com/adamw/reactmq/blob/master/src/main/scala/com/reactmq/Sender.scala
Adam
On Thursday, October 30, 2014 12:04:23 PM UTC+1, Akka Team wrote:
Hi Adam,
I'm not running Windows (MacOS
stream)
source -- trans1 -- broadcast --
\--- sink2 (on
complete drain)
Will the failure of sink1 propagate to a completion of the whole stream? In
theory it could continue in a crippled way (with only one branch
remaining).
Thanks!
Adam
.
--
Thanks,
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups Akka
One easy way is to extend UntypedActor, override whatever methods you need
with final methods and provide your own callback methods for overriding by
sub classes.
The slightly messy part of this is that you’ll be forced to provide
callback method names with different names (e.g.
out my application with jHiccup (which Adam suggested)
running for a day and it seems that the highest hiccup duration is 65
milliseconds. It is acceptable for my application ( but it will not be, if I
try to implement the realtime part I was asking for ) A friend of mine also
suggested checking
There is also an option of trying the Zing JVM from Azul. It's not free, but
depending on your case, it might end up being cheaper in the overall, assuming
it does what they claim - I've never used it myself, only talked to other
people who were using it.
Also it's possible for some
You cannot have separate cpu and heap metrics for nodes within the same JVM.
OSGI won't help either - it mostly achieves containment through complex class
loaders.
You could sort of have an approximiation of CPU consumption per node by summing
up the thread cpu consumption for the related
to 2.3.6 it makes no different
On 23 September 2014 23:15, Tim Pigden tim.p...@optrak.com javascript:
wrote:
2.11.2 (akka 2.3.4)
scalacOptions := Seq(-feature, -deprecation, -encoding, utf8,
-Xlint)
On 23 September 2014 21:26, Adam adam...@gmail.com javascript:
wrote:
Interesting.
Which
is a Sink type now, which I don't really understand :). Is there
some different way to implement foreach? (the foreach usage I have is to
handle connections from stream-tcp)
Thanks,
Adam
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current
Got it, thanks! Updated the code :)
Adam
On Wednesday, September 17, 2014 2:50:23 PM UTC-7, Konrad Malawski wrote:
Hello Adam,
yes, there is: .withSink(ForeachSink(el = ).run()
The sink also holds a future which you can watch for completion, see:
http://doc.akka.io/api/akka-stream
(by akka.io, I meant the IO package of akka
http://doc.akka.io/docs/akka/2.3.5/scala/io.html, of course...)
On Tuesday, September 2, 2014 4:06:56 PM UTC+3, Adam wrote:
Hi,
I'm not sure how using protobuf forces you to communicate in a blocking
manner.
I'm also using it but over akka.io
Hi,
One more follow up question.
When using the setting advised by the documentation for this scenario
(http://doc.akka.io/docs/akka/snapshot/java/logging.html#SLF4J) the only
real gap from what I need is that with akka.logLevel set to DEBUG and with
the SLF4J binding configured to INFO,
Hi,
I know Akka's configuration does not get reloaded at run-time (see here
https://groups.google.com/forum/#!msg/akka-user/bQA1zJP3yOY/fBVmGfRvYUYJ).
It is however quite a common use case for logger settings to be re-loadable
at run-time.
Is there any way to achieve this?
--
Read the
Hi,
Is there a way to change socket options such as send receive buffers from
the Java API?
All I can find is the set of Scala case classes (e.g.
http://doc.akka.io/api/akka/snapshot/index.html#akka.io.Inet$$SO$$SendBufferSize),
but to the best of my knowledge there is no way to use case
1 - 100 of 121 matches
Mail list logo
