perfsonar-user - Re: [perfsonar-user] Maddash Deployment
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Brian Candler <>
- To: Muhammad Tayyab <>, "" <>
- Subject: Re: [perfsonar-user] Maddash Deployment
- Date: Mon, 18 Feb 2019 13:56:14 +0000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=Pd/RSc MuLFiQI6J6e1PnxtFlJ4KdTegIH5/18pUHjHdbQSkzyo47gHQ+I8nvfVR1B9S8gS U5SFS9BDE/pDKHrIeCbiJ09T4DqgNeeQkSU59aYyW4of3T0RKquhakT/Dd3f9v0R e10cg7u3c3Sc8bfyHJaYLYvOZgA1z/ntKDTdc=
On 18/02/2019 06:03, Muhammad Tayyab wrote:
I am doing POC of perfSONAR deployment in our network and we are planning to deploy around 60 nodes. Looking forward for hardware requirement for the Maddash dashboard with 60 nodes CPU/RAM/Storage.
The dashboard itself does almost nothing. Well, it's written in Java, and even "hello world" in Java needs 2GB RAM :-) But it stores very little, and only checks results every 15 minutes. I would just throw it in a VM.
If you want a central measurement archive, where all the nodes post their test results back to the archive instead of storing them locally, that's a different matter. Even then: the measurement archive and the dashboard don't have to be on the same machine.
- [perfsonar-user] Maddash Deployment, Muhammad Tayyab, 02/18/2019
- Re: [perfsonar-user] Maddash Deployment, Brian Candler, 02/18/2019
Archive powered by MHonArc 2.6.19.