On 10/14/2013 01:11 PM, Tregaron Bayly wrote:
It was something else. Using strace and strace -c we could see that targetcli was doing several times the number of syscalls strictly necessary to parse out all the configfs nodes and their values - opening and closing the same files over and over again. We wrote the skinniest code we could to simply spin through and then write the correct JSON and it allowed us to scale it up. This may have been improved now as it was a year ago that we were building this all out but the saveconfig time and slow lvm processing were the biggest challenges we had to overcome.
The saveconfig (restoreconfig?) performance thing I think was addressed in January 2013. So, very interested if any reports using rtslib-fb28 or later.
Slow LVM processing? Can you elaborate on the issue and how you overcame it? (Sorry if a little OT.) Were you using lvmetad?
Any other pain points from anyone, besides the stuff you all mentioned already? Usability or other stuff you miss from using other targets?
Regards -- Andy -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
