magine it causing degradation if the configuration files are super big /
> some other weird cases.
>
>
> --
> *From:* Krishna Kishore Bonagiri
> *To:* user@hadoop.apache.org
> *Sent:* Wednesday, August 7, 2013 10:03 AM
> *Subject:* Re: Extra st
Kishore Bonagiri
To: user@hadoop.apache.org
Sent: Wednesday, August 7, 2013 10:03 AM
Subject: Re: Extra start-up overhead with hadoop-2.1.0-beta
Hi Omkar,
Can you please see if you can answer my question with this info or if you need
anything else from me?
Also, does resource localization
Hi Omkar,
Can you please see if you can answer my question with this info or if you
need anything else from me?
Also, does resource localization improve or impact any performance?
Thanks,
Kishore
On Thu, Aug 1, 2013 at 11:20 PM, Omkar Joshi wrote:
> How are you making these measurements ca
Hi Omkar,
I have got these number by running a simple C program on the containers
that fetches the timestamp in microseconds and exits. The times mentioned
are low and high, they are not varying so drastically with in a version but
there are huge differences(like a second) between the two versio
How are you making these measurements can you elaborate more? Is it on a
best case basis or on an average or worst case? How many resources are you
sending it for localization? were the sizes and number of these resources
consistent across tests? Were these resources public/private/application
spec
Hi,
Please share with me if you anyone has an answer or clues to my question
regarding the start up performance.
Also, one more thing I have observed today is the time taken to run a
command on a container went up by more than a second in this latest version.
When using 2.0.4-alpha, it used to
