Topic: CGMiner API call 'devs' response limited to about 149 devices? (Read 1207 times)
You could use gpu|N, pga|N, and asc|N to get values for truncated devices. Not ideal for a ton of devices but it provides the same info as devs. And not using json should save you some characters and may be able to fit more devices in devs before truncating?
I'm running some cgminer instances with a large number of devices.
I find that when I use the 'devs' API call, information is only returned for the first 149 devices on one machine (first 147 on another), although the response is a proper JSON structure, and is not truncated.
This is with cgminer 3.1.0 and 3.2.0. I have not yet tried the latest.
Is this known behavior?
You will also find if you use json it says "id":0 for truncated outputI find that when I use the 'devs' API call, information is only returned for the first 149 devices on one machine (first 147 on another), although the response is a proper JSON structure, and is not truncated.
This is with cgminer 3.1.0 and 3.2.0. I have not yet tried the latest.
Is this known behavior?
Yes it makes sure it's still at a valid point and truncates it before 65432 bytes
("id":1 for normal/full output)
I'm running some cgminer instances with a large number of devices.
I find that when I use the 'devs' API call, information is only returned for the first 149 devices on one machine (first 147 on another), although the response is a proper JSON structure, and is not truncated.
This is with cgminer 3.1.0 and 3.2.0. I have not yet tried the latest.
Is this known behavior?
I find that when I use the 'devs' API call, information is only returned for the first 149 devices on one machine (first 147 on another), although the response is a proper JSON structure, and is not truncated.
This is with cgminer 3.1.0 and 3.2.0. I have not yet tried the latest.
Is this known behavior?
Jump to: