For performance reasons, I would suggest keeping SettingName values relatively short and each module's entries in the ModuleSettings or TabModuleSettings tables relatively few in number. With that many settings specific to your module, I would suggest defining your own module ConfigurationInfo class, configuration table (s), and the needed stored proceedures for updating and accessing them.  This also makes it much easier to access module settings when needed in your sql stored proceedures.

If the settings are primarily related to customization of the module's layout, then look into using a templated design with tokens for field values, etc.

Thanks for your answer. I have a question though: how using my own tables (over the TabModuleSettings table itself) to store those settings increases the performance ?

As far as "templated design" is concerned, do you have any pointer on a tutorial?

Thanks