Add validation on watchset importing (estimate RAM needed)

[vaspa]

A watchset that does not fit the watch memory should not pass the validation.
An estimation of RAM needed and actual RAM limit should be shown to the user. So the user could adjust his watchset definition to fit the RAM requirements.

[althink]

I'm aware that this is quite important but unfortunately at this stage is
not possible. Memory usage is changing from day to day and the biggest
issue is that malloc is allocating a little bit more memory that is
required and there's no standard how much will it be. So there are many
factors that affect that. And I have to change it one more time to run your
weather watchset because it's too big for latest snapshot.

On Fri, Dec 4, 2015 at 3:41 PM, Pavel Vasilyev [email protected]
wrote:

A watchset that does not fit the watch memory should not pass the
validation.
An estimation of RAM needed and actual RAM limit should be shown to the
user. So the user could adjust his watchset definition to fit the RAM
requirements.

—
Reply to this email directly or view it on GitHub
#22.

[vaspa]

Of course it will wait for a stable version.
BTW I don't use the weather watchset, it is just a challenge for testing purposes ;)

Is it right that the external properties values are stocked in the external RAM now?