shadowlin
67 Posts
Quote from shadowlin on March 20, 2018, 8:52 am
Is it limited by software or hardware?
Is it limited by software or hardware?
admin
2,930 Posts
Quote from admin on March 20, 2018, 9:31 am
There is a software limit determined by the kernel, it is something like 2^16 per host. Some hardware SAN do have a limit of 256 targets per adaptor. Practically we do not recommend more than this per node.
There is a software limit determined by the kernel, it is something like 2^16 per host. Some hardware SAN do have a limit of 256 targets per adaptor. Practically we do not recommend more than this per node.
shadowlin
67 Posts
Quote from shadowlin on March 21, 2018, 6:15 am
I see.
What kind of hardware is needed to support 256 target per node?
I see.
What kind of hardware is needed to support 256 target per node?
admin
2,930 Posts
Quote from admin on March 21, 2018, 11:02 am
This is dependent on the client workload. A single target / lun disk can saturate your node resources depending on application io load, this is not a bad thing if your application requires all the performance it can get.
If you tell me more about your environment i could help you better.
This is dependent on the client workload. A single target / lun disk can saturate your node resources depending on application io load, this is not a bad thing if your application requires all the performance it can get.
If you tell me more about your environment i could help you better.
shadowlin
67 Posts
Quote from shadowlin on March 27, 2018, 4:22 am
The client workload won't be very intensive,but there will be a lot of clients.
if the total throughput is 2.5GB/s then every target's throughput would be like 10MB/s.
My most concern is if the total throughput is the same how many targets can a node(for iscsi only with no mon or osd) handle and what kind of resource is needed.
Thanks
The client workload won't be very intensive,but there will be a lot of clients.
if the total throughput is 2.5GB/s then every target's throughput would be like 10MB/s.
My most concern is if the total throughput is the same how many targets can a node(for iscsi only with no mon or osd) handle and what kind of resource is needed.
Thanks
admin
2,930 Posts
Quote from admin on March 27, 2018, 8:49 am
The 2.5GB/s is your throughput per node, it is all dependent on node resources. It is not related to how many targets. As stated you can have 1 target that needs to read 5GB/s, your node will not be able to handle this single target itself. In your case i would forget the 256 recommendation, and look at your client workload and put as many targets per node within the node capability. So if your clients were average 5MB/s i would put 512 targets per node.
The 2.5GB/s is your throughput per node, it is all dependent on node resources. It is not related to how many targets. As stated you can have 1 target that needs to read 5GB/s, your node will not be able to handle this single target itself. In your case i would forget the 256 recommendation, and look at your client workload and put as many targets per node within the node capability. So if your clients were average 5MB/s i would put 512 targets per node.
shadowlin
67 Posts
Quote from shadowlin on March 29, 2018, 1:38 am
Is it safe to say If I can get 1GB/s throughput for one target then it would be ok to have 100 targets with 10MB/s throughput for each target.
How much resource would be needed for the targets themselves?Is it possible that the throughput is enough but the node need more memory and cpu to support the targets.
Is it safe to say If I can get 1GB/s throughput for one target then it would be ok to have 100 targets with 10MB/s throughput for each target.
How much resource would be needed for the targets themselves?Is it possible that the throughput is enough but the node need more memory and cpu to support the targets.
admin
2,930 Posts
Quote from admin on March 29, 2018, 10:39 am
Yes it will be OK. The total client load is what you need to account for.
Yes it will be OK. The total client load is what you need to account for.
