Serialization and resource manager are not involved in CONTAINER_LOCAL.
However, CONTAINER_LOCAL is probably not what you want, since it would
force all partitions to run in the same JVM.
Thomas
On Fri, Dec 22, 2017 at 1:19 PM, Ananth G wrote:
> I guess my comment below regarding overhead of
I guess my comment below regarding overhead of serialisation in container local
is wrong ? Nevertheless having a local thread implementation gives some
benefits . For example I am using to whether sleep if there is no request in
the queue or spin checking for request presence in the request queu
On Fri, Dec 22, 2017 at 8:19 AM, Vlad Rozov wrote:
> I don't see more complexity in implementing a plugin compared to
> implementing an application. Additionally, for the use case you mention,
> plugin is a better option, as likely the behavior applies not to a single
> application, but all appli
Thanks for the comments Thomas and Pramod.
Apologies for the delayed response on this thread.
> I believe the thread implementation still adds some value over a container
> local approach. It is more of a “thread local” equivalent which is more
> efficient as opposed to a container local imp
I am thinking of a boolean property named "apex.run.simulate"
On Thu, Dec 21, 2017 at 9:05 AM, Sanjay Pujare
wrote:
> It is relatively easy to describe the justification for this change without
> getting into the weeds and hairsplitting words.
>
> A DAG is built not only to launch an application
I don't see more complexity in implementing a plugin compared to
implementing an application. Additionally, for the use case you mention,
plugin is a better option, as likely the behavior applies not to a
single application, but all applications in that environment.
Websocket gateway address i
