Am 18.04.2013 um 06:32 schrieb Dietmar Maurer :
>> Then let's go this way. It's much simpler than adding RRD.
>>
>> So the question is should this be a completely new call
>
> Yes, I think this should be a new call:
>
> GET /nodes//netstat
>
> [
> {vmid => 100, dev => net0, in => XXX, out =>
> Oh ok sorry didn't know that. I can change it but i don't see any useful
> usage to
> display these values. They're just counters rising up to 64bit and then reset
> through the lifetime of a VM. I think without useful deltas and history there
> is no
> usage. But i can still change it if you w
Am 18.04.2013 08:35, schrieb Dietmar Maurer:
Patch sent. I used a different output format which has the vmid as a key so it
is
easier to access the right information as nobody needs to loop through the
array.
But that format does not work with an ExtJS grid widget (in case someone wants
to di
> Patch sent. I used a different output format which has the vmid as a key so
> it is
> easier to access the right information as nobody needs to loop through the
> array.
But that format does not work with an ExtJS grid widget (in case someone wants
to display it on the GUI)?
_
Am 18.04.2013 06:32, schrieb Dietmar Maurer:
Then let's go this way. It's much simpler than adding RRD.
So the question is should this be a completely new call
Yes, I think this should be a new call:
GET /nodes//netstat
[
{vmid => 100, dev => net0, in => XXX, out => YYY},
{vmid => 100, dev =
> Then let's go this way. It's much simpler than adding RRD.
>
> So the question is should this be a completely new call
Yes, I think this should be a new call:
GET /nodes//netstat
[
{vmid => 100, dev => net0, in => XXX, out => YYY},
{vmid => 100, dev => net1, in => XXX, out => YYY},
{vmid =>
Am 17.04.2013 16:39, schrieb Dietmar Maurer:
3000 VMs all with 32 nics seems unrealistic to me.
BTW, we have several users with >500VMs, so I guess we can easily reach that
limit.
Sure but those won't have 32 NICs. So if we go the way one file per NIC.
We might have 3800 files for 3000 VMs. (
> >> 3000 VMs all with 32 nics seems unrealistic to me.
> >
> > BTW, we have several users with >500VMs, so I guess we can easily reach that
> limit.
>
> Sure but those won't have 32 NICs. So if we go the way one file per NIC.
> We might have 3800 files for 3000 VMs. (800 VMs with 2 Nics so they h
Hi,
Am 17.04.2013 14:42, schrieb Adrian Costin:
> I'm sorry to dropping in, but isn't Proxmox already counting traffic in
> it's internal RRD? Couldn't the "rrddata" API call be used to retrieve
> the data in the RRD externally and process it to count the total
> bandwidth used in 1 month?
>
> May
I'm sorry to dropping in, but isn't Proxmox already counting traffic in
it's internal RRD? Couldn't the "rrddata" API call be used to retrieve the
data in the RRD externally and process it to count the total bandwidth used
in 1 month?
Maybe I've misunderstood what the issue is here...
Best rega
Am 17.04.2013 14:17, schrieb Dietmar Maurer:
>> Nowhere ;-) how about just return the counter values for the correct tap
>> device
>> through API?
>>
>> So it is basically:
>> 1.) a wrapper from netX to correct tap
>> 2.) query tap counter inout / output values
>> 3.) allow to query this through A
Am 17.04.2013 14:11, schrieb Dietmar Maurer:
>> How have you calculated your 3000 Files?
>>
>> 3000 VMs all with 32 nics seems unrealistic to me.
>
> BTW, we have several users with >500VMs, so I guess we can easily reach that
> limit.
Sure but those won't have 32 NICs. So if we go the way one f
> Nowhere ;-) how about just return the counter values for the correct tap
> device
> through API?
>
> So it is basically:
> 1.) a wrapper from netX to correct tap
> 2.) query tap counter inout / output values
> 3.) allow to query this through API
>
> So it is at least possible to implement traf
Am 17.04.2013 14:09, schrieb Dietmar Maurer:
>> How have you calculated your 3000 Files?
>>
>> 3000 VMs all with 32 nics seems unrealistic to me.
>
> I simply want to show you that this can overload all! servers inside a
> cluster by
> just writing rrd files. I am not keen to spend any resources
> How have you calculated your 3000 Files?
>
> 3000 VMs all with 32 nics seems unrealistic to me.
BTW, we have several users with >500VMs, so I guess we can easily reach that
limit.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxm
> How have you calculated your 3000 Files?
>
> 3000 VMs all with 32 nics seems unrealistic to me.
I simply want to show you that this can overload all! servers inside a cluster
by
just writing rrd files. I am not keen to spend any resources on that task.
> Another way could be to just allow to
Am 17.04.2013 13:52, schrieb Dietmar Maurer:
>> But on IDE with 3000 Files it doesn't work every 10s. At least without
>> rrdcache.
>> But that sounds in general a way to much for such a HW.
>
> So maybe it is a bad idea to use rrd for that purpose - any other suggestions?
How have you calculate
> But on IDE with 3000 Files it doesn't work every 10s. At least without
> rrdcache.
> But that sounds in general a way to much for such a HW.
So maybe it is a bad idea to use rrd for that purpose - any other suggestions?
___
pve-devel mailing list
pve
Am 17.04.2013 09:44, schrieb Dietmar Maurer:
>>> I am particularly interested in IO load (on normal ide disks) and memory
>> requirements of rrdcached.
>>
>> Don't have IDE Disks at all. Can only provide SSD or SAS or SATA2 Disks.
>
> I know that you have quite fast hardware. But we need to test o
> > I am particularly interested in IO load (on normal ide disks) and memory
> requirements of rrdcached.
>
> Don't have IDE Disks at all. Can only provide SSD or SAS or SATA2 Disks.
I know that you have quite fast hardware. But we need to test on 'normal'
hardware.
Testing IO on SSDs makes no s
Am 17.04.2013 09:28, schrieb Dietmar Maurer:
>> Sure but how to benchmark? Just create a file with 32 values and create
>> 2 files (this but be the avg of network interfaces) may be it is just 1.5.
>>
>> And then update both each second and look at the disk i/o? Or how did you
>> imagine this. I th
> Sure but how to benchmark? Just create a file with 32 values and create
> 2 files (this but be the avg of network interfaces) may be it is just 1.5.
>
> And then update both each second and look at the disk i/o? Or how did you
> imagine this. I think it makes no sense to compare 32 values agains
Am 17.04.2013 09:08, schrieb Dietmar Maurer:
>>> It is still not clear if we want a single file, or multiple files. I
>>> guess this requires careful evaluation. How does such system behave
>>> when we have 3000VMs? We need to test that before we go further.
>>
>> Oh i thought a single file contain
> > It is still not clear if we want a single file, or multiple files. I
> > guess this requires careful evaluation. How does such system behave
> > when we have 3000VMs? We need to test that before we go further.
>
> Oh i thought a single file containing 32 net in/out values. I've no idea how
>
Am 17.04.2013 07:24, schrieb Dietmar Maurer:
>
>> Am 12.03.2013 18:53, schrieb Dietmar Maurer:
Why does a single file creates less load? Both contain the same amount of
>> data.
>>>
>>> A VM can use up to 32 network devices. Updating 32 files create more load
>> than updating a single file?
>
> Am 12.03.2013 18:53, schrieb Dietmar Maurer:
> >> Why does a single file creates less load? Both contain the same amount of
> data.
> >
> > A VM can use up to 32 network devices. Updating 32 files create more load
> than updating a single file?
>
> I want to proceed with this one. First i need
Am 12.03.2013 18:53, schrieb Dietmar Maurer:
>> Why does a single file creates less load? Both contain the same amount of
>> data.
>
> A VM can use up to 32 network devices. Updating 32 files create more load
> than updating a single file?
I want to proceed with this one. First i need to know h
> > File size does not really matters if within a reasonable size.
>
> Hopefully i created tjhe file correctly ;-) it takes 1,1MB.
Current files seem to take about 6KB per value, so I would estimate 2*32*6KB =
384KB.
So why is it that large?
___
pve-de
Hi,
Am 13.03.2013 07:17, schrieb Dietmar Maurer:
>>> How large is a file to store 32 netin/netout values with our setup?
>>>
>> No idea.I can check this if you want.
>
> Please do
>
>> but this means we always have a bigger file
>> cause most vms have just one or two network cards.
>
> File si
> > How large is a file to store 32 netin/netout values with our setup?
> >
> No idea.I can check this if you want.
Please do
> but this means we always have a bigger file
> cause most vms have just one or two network cards.
File size does not really matters if within a reasonable size.
_
oxmox.com
>> Subject: Re: [pve-devel] Count monthly traffic
>>
>>
>> Am 12.03.2013 16:28, schrieb Dietmar Maurer:
>>>> Yes, I think it make sense. Like this we can avoid to write null
>>>> values for non existant network card.
>>>> I don&
> -Original Message-
> From: Stefan Priebe - Profihost AG [mailto:s.pri...@profihost.ag]
> Sent: Dienstag, 12. März 2013 16:32
> To: Dietmar Maurer
> Cc: Alexandre DERUMIER; pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] Count monthly traffic
>
>
> A
> Why does a single file creates less load? Both contain the same amount of
> data.
A VM can use up to 32 network devices. Updating 32 files create more load than
updating a single file?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.
Why does a single file creates less load? Both contain the same amount of data.
Am 12.03.2013 um 16:49 schrieb Dietmar Maurer :
>> Yes - just let me know what you prefer. Internally we create one .rrd for
>> every
>> interface, disk, ... for our normal physikal servers. This is very flexible
>>
> Yes - just let me know what you prefer. Internally we create one .rrd for
> every
> interface, disk, ... for our normal physikal servers. This is very flexible
> and you
> even do not need new folders and bumps in status.c.
I am concerned about the load on the rrd server. Each new file increas
Am 12.03.2013 16:28, schrieb Dietmar Maurer:
>> Yes, I think it make sense. Like this we can avoid to write null values for
>> non
>> existant network card.
>> I don't know if Dietmar have an opinion about this.
>
> The suggestion was to create one new file (to store 64 new values).
> Another op
> Yes, I think it make sense. Like this we can avoid to write null values for
> non
> existant network card.
> I don't know if Dietmar have an opinion about this.
The suggestion was to create one new file (to store 64 new values).
Another option would be one new file per network interface?
__
So we have an rrd for each network card?
Yes, I think it make sense. Like this we can avoid to write null values for non
existant network card.
I don't know if Dietmar have an opinion about this.
- Mail original -
De: "Stefan Priebe - Profihost AG"
À: "Alexandre D
;
>
> - Mail original -
>
> De: "Stefan Priebe"
> À: "Dietmar Maurer"
> Cc: "Alexandre DERUMIER" , pve-devel@pve.proxmox.com
> Envoyé: Lundi 11 Mars 2013 21:32:23
> Objet: Re: [pve-devel] Count monthly traffic
>
> Hi,
>
> so 32 netin && 32 netout values.
>
> does null values take space in rrd ?
yes (space is fixed but pre-allocated).
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
pt some values which are skipped (status.c) and not writen to rrd, but
only keep in memory, like "running" value for example)
- Mail original -
De: "Stefan Priebe"
À: "Dietmar Maurer"
Cc: "Alexandre DERUMIER" , pve-devel@pve.proxmox.com
Envoy
Hi,
Am 11.03.2013 16:23, schrieb Dietmar Maurer:
do i need to add pve2.4?
next version will be 3.0 ;-)
This will require some low level C hacking in pve-cluster/data/src/status.c
(search for rrd).
We need to create a new rrd definition, and we can use key 'pve3-vmnet'.
Just tell if you need
roxmox.com, "Stefan Priebe"
Envoyé: Lundi 11 Mars 2013 17:00:51
Objet: RE: [pve-devel] Count monthly traffic
> disk io stats could be also interesting.
>
> Currently we have rd_bytes/wr_bytes counters but not
> rd_operations/wr_operations counters.
First step is to def
> disk io stats could be also interesting.
>
> Currently we have rd_bytes/wr_bytes counters but not
> rd_operations/wr_operations counters.
First step is to define the RRD file format. As you know, it is hard to change
rrd files later, so we need to do that very carefully.
We should also try to
voyé: Lundi 11 Mars 2013 16:23:10
Objet: RE: [pve-devel] Count monthly traffic
> do i need to add pve2.4?
next version will be 3.0 ;-)
This will require some low level C hacking in pve-cluster/data/src/status.c
(search for rrd).
We need to create a new rrd definition, and we can use key
> do i need to add pve2.4?
next version will be 3.0 ;-)
This will require some low level C hacking in pve-cluster/data/src/status.c
(search for rrd).
We need to create a new rrd definition, and we can use key 'pve3-vmnet'.
Just tell if you need more help.
+=
$netdev->{$dev}->{transmit}; }
So for the moment it's not possible.
Maybe can we improve stats with more detailled values for each nics,
each disk && each cpu cores ?
- Mail original -
De: "Stefan Priebe - Profihost AG" À:
pve-devel@pve.proxmox.com En
can we improve stats with more detailled values for each nics,
each disk && each cpu cores ?
- Mail original -
De: "Stefan Priebe - Profihost AG" À:
pve-devel@pve.proxmox.com Envoyé: Samedi 9 Mars 2013 10:48:46 Objet:
[pve-devel] Count monthly traffic
Is
> Maybe can we improve stats with more detailled values for each nics, each disk
> && each cpu cores ?
I would prefer to implement only what we need. I guess an additional RRD file
for nics would be no problem.
___
pve-devel mailing list
pve-devel@pve.p
> > You will end up developing a monitoring application. And the amount of
> > data you need to store will also grow considerable.
> >
> > @Stefan: Maybe you can gather those information yourself reading
> /proc/net/dev/?
>
> Will have a look most probably yes. I just need to know which tap is whi
Am 09.03.2013 um 15:08 schrieb Dietmar Maurer :
>> Maybe can we improve stats with more detailled values for each nics, each
>> disk
>> && each cpu cores ?
>
> You will end up developing a monitoring application. And the amount of data
> you need to
> store will also grow considerable.
>
> @S
..@pve.proxmox.com [mailto:pve-devel-
>> boun...@pve.proxmox.com] On Behalf Of Dietmar Maurer
>> Sent: Samstag, 09. März 2013 14:55
>> To: Alexandre DERUMIER; Stefan Priebe - Profihost AG
>> Cc: pve-devel@pve.proxmox.com
>> Subject: Re: [pve-devel] Count monthly traffic
&g
> Maybe can we improve stats with more detailled values for each nics, each disk
> && each cpu cores ?
You will end up developing a monitoring application. And the amount of data you
need to
store will also grow considerable.
@Stefan: Maybe you can gather those information yourself reading /pro
bject: Re: [pve-devel] Count monthly traffic
>
> >
> > $d->{netout} += $netdev->{$dev}->{receive};
> > $d->{netin} += $netdev->{$dev}->{transmit};
> > }
> >
> >
> > So for the moment it's not possible.
>
>
>
> $d->{netout} += $netdev->{$dev}->{receive};
> $d->{netin} += $netdev->{$dev}->{transmit};
> }
>
>
> So for the moment it's not possible.
Why is it not possible? You can simply query the rrd database?
___
pve-devel mailing list
host AG"
À: pve-devel@pve.proxmox.com
Envoyé: Samedi 9 Mars 2013 10:48:46
Objet: [pve-devel] Count monthly traffic
Is there a way to get monthly traffic per nic per vm?
Stefan
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http:
Is there a way to get monthly traffic per nic per vm?
Stefan
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
57 matches
Mail list logo
