-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29/10/13 17:12, Kapil Thangavelu wrote:
fwiw, the mysql charm tries to address this with a shared-db
interface, and a separate admin interface. ie the shared-db
interface shares out the same db user/password to multiple
services, and then for
On Wed, Oct 30, 2013 at 10:47 AM, Gustavo Niemeyer gust...@niemeyer.netwrote:
On Wed, Oct 30, 2013 at 7:35 AM, Kapil Thangavelu
kapil.thangav...@canonical.com wrote:
Just thinking outloud, but In the active-active db scenario, there's an
available db for the charm to store this info. ie.
A very spooky charm status!!
## General Info
- [Pad](http://pad.ubuntu.com/7mf2jvKXNa)
- [Status
Board](https://trello.com/board/charmers-board/4ec1696da3f94bd2ea5b2b01)
- [Juju.u.c Meeting
Site](https://juju.ubuntu.com/community/weekly-charm-meeting/)
- [Video of
I'm told that's for a network (veth nic?) performance issue? FWIW
my main build+test box is running on 3.2 precise kernel with
ubuntu-lxc daily ppa. overlayfs and lvm clones work perfectly out
of the box, and btrfs (which i'm using now) only have the fsync
performance issue, which I work around
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to put together a quick summary of what I've found out so
far with testing juju in an environment with thousands (5000+) agents.
1) I didn't ever run into problems with connection failures due to
socket exhaustion. The default upstart
On Wed, Oct 30, 2013 at 6:23 AM, John Arbash Meinel
j...@arbash-meinel.com wrote:
I'm trying to put together a quick summary of what I've found out so
far with testing juju in an environment with thousands (5000+) agents.
Great testing, John.
2) Agents seem to consume about 17MB resident
On Wed, Oct 30, 2013 at 9:23 AM, John Arbash Meinel
j...@arbash-meinel.comwrote:
2) Agents seem to consume about 17MB resident according to 'top'. That
should mean we can run ~450 agents on an m1.large. Though in my
testing I was running ~450 and still had free memory, so I'm guessing
there
Hi John,
This is awesome, its great to see this scale testing and analysis. Some
additional questions/comments inline.
On Wed, Oct 30, 2013 at 6:23 AM, John Arbash Meinel
j...@arbash-meinel.comwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to put together a quick summary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
- From what I can tell, all units take out a watch on their
service so that they can monitor its Life and CharmURL. However,
adding a unit to a service triggers a change on that service,
even though Life and CharmURL haven't changed. If we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
4) If I bring up the units one by one (for i in `seq 500`; do for j
in `seq 10` do juju add-unit --to $j ; time wait; done), it ends
up triggering O(N^2) behavior in the system. Each unit agent seems
to have a watcher for other units of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-10-30 18:11, Nate Finch wrote:
On Wed, Oct 30, 2013 at 9:23 AM, John Arbash Meinel
j...@arbash-meinel.com mailto:j...@arbash-meinel.com wrote:
2) Agents seem to consume about 17MB resident according to 'top'.
That should mean we can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
The log size didn't come up again in this email. Not sure if you
meant separately or just got lost in the message length.
I didn't explicitly enumerate it, but it is because of section (4).
Namely, bringing up 1000 units triggers 1000*1000
12 matches
Mail list logo
