On 09/29/2014 07:32 PM, Mark Levedahl wrote:
It amazes me that one Cobbler server can handle hundreds of systems
storing its objects in the
file system and loading all of them to RAM at Cobbler startup. I'd
expect a database backend and a
on-demand load for that degree of scalability.
Regards,
Alan Evangelista
I have about 150 systems in one cobbler instance, 70 in another, never
thought about memory size. I've been saved many times by having
backups of the text files and being able to restore those individually
or just directly edit them. A single machine occupies at most a couple
of kbytes of memory, even with thousands of machines, you're just
barely into needing mbytes of memory in an era when cell phones have
gbytes. Using a database here is just a solution looking for a problem.
Mark, I agree. I come from a background where RAM/processor power is
limited, so I tend
to focus in performance. Indeed it does not matter here.
This makes me think if we need the couch/mongodb serializers...
Regards,
Alan Evangelista
_______________________________________________
cobbler-devel mailing list
cobbler-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel
