Not exactly the Enterprise oriented benchmark, but may give some insight
though.
https://mesos.apache.org/documentation/latest/powered-by-mesos/
https://www.youtube.com/watch?v=LQxnuPcRl4st=1m31s
On Wed, Mar 4, 2015 at 2:18 AM, Diego Medina di...@fmpwizard.com wrote:
Well, I deeply think that
Hi Diego,
You're welcome ;-)
Well, I deeply think that additionally to the architecture and the
organisations concerns, Mesos need to provide some Enterprise oriented
benchmark and proof to be able to really prime time on the enterprise
world and not only on the Startup style enterprises, but
Well, I deeply think that additionally to the architecture and the
organisations concerns, Mesos need to provide some Enterprise oriented
benchmark and proof to be able to really prime time on the enterprise
world and not only on the Startup style enterprises, but it's not the
topic of your
Thanks Billy, typo fixed
https://github.com/fmpwizard/owlcrawler/commit/c57750756310b228e7eab4d3a9b5f7be0f07a574
Mesos platform VS Bare-metal
I don't have any near future plans on benchmarking, but what do you mean by
bare-metal, like, running the crawler without using mesos to distribute the
Hi Diego, did you already plan to make a benchmark of your result on the
Mesos platform VS Bare-metal servers ?
It would be really interesting for Enterprise evangelism, they love
benchmark and metrics.
I'm impress by your project and how it goes fast. I'm myself a fan of
Golang, but why did you
Diego,
I've checked your code, nice effort! Great to see people hacking with mesos
and go bindings!
One thing though. You do the actual job in the launchTask() of your
executor. This prevents you from multiple tasks in parallel on one
executor. That means you can't have more simultaneous tasks
Hi diego, as a real fan of the golang, I'm cudoes and clap for your work on
this distributed crawler and hope you'll finally release it ;-)
About your question, the common architecture is to have one scheduler and
multiple executors rather than one big executor.
The basics of mesos is to take any
@John: thanks for the link, i see that RENDLER uses the ExecutorId from
ExecutorInfo to decide what to do, I'll give this a try
@Craig: you are right, after I sent the email I continued to read more of
the mesos docs and saw that I used the wrong term, where I meant scheduler
instead of framework,
8 matches
Mail list logo
