Hi CommCarers
I'm seeking clarity on whether the amount of case properties that you have
make a difference to the load that is placed on the mobile device (even if
these properties are not added to case detail or case list)? I am
interested, because for our app we want to overlay our basic activity
information with some in-depth baseline surveys. One option is to save each
of the survey questions (about 100) to case properties. This could help
with analysis later, particularly when comparing changes between baseline
and endline surveys as I can use case export for this. However, if it adds
burden to the phones then it's probably best to not add these to case data.
Is there a general rule of thumb about the appropriate maximum number of
case properties to be attached to each case?
Thanks!
John
John,
Unfortunately this number is actually fairly hard for us to set a specific
ceiling on. The performance implications of this depends a lot on how many
cases you're supporting per device, what kinds of lookups/searches you're
doing on them, etc.
In general it is true that certain operations take a performance hit when
the number of case properties is extended, since we store them flexibly. In
most apps the only specific place you would expect to see this would be
when you view the case list, and any time you perform a search against
unindexed properties, which you'd have to do with advanced expressions.
In my experience on most phones having on-the-order of 100-200 case
properties has been performant for most apps, but it will definitely depend
a bit on how they are being used.
-Clayton
···
On Tue, Sep 8, 2015 at 1:15 PM, John Skelton wrote:
Hi CommCarers
I'm seeking clarity on whether the amount of case properties that you have
make a difference to the load that is placed on the mobile device (even if
these properties are not added to case detail or case list)? I am
interested, because for our app we want to overlay our basic activity
information with some in-depth baseline surveys. One option is to save each
of the survey questions (about 100) to case properties. This could help
with analysis later, particularly when comparing changes between baseline
and endline surveys as I can use case export for this. However, if it adds
burden to the phones then it's probably best to not add these to case data.
Is there a general rule of thumb about the appropriate maximum number of
case properties to be attached to each case?
Thanks!
John
--
You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Clayton,
Thanks for the information. I understand that it depends on many different
factors, but its good to know that 100-200 case properties is not generally
considered extravagant.
John.
···
On Thu, Sep 10, 2015 at 3:05 PM, Clayton Sims wrote:
John,
Unfortunately this number is actually fairly hard for us to set a specific
ceiling on. The performance implications of this depends a lot on how many
cases you're supporting per device, what kinds of lookups/searches you're
doing on them, etc.
In general it is true that certain operations take a performance hit when
the number of case properties is extended, since we store them flexibly. In
most apps the only specific place you would expect to see this would be
when you view the case list, and any time you perform a search against
unindexed properties, which you'd have to do with advanced expressions.
In my experience on most phones having on-the-order of 100-200 case
properties has been performant for most apps, but it will definitely depend
a bit on how they are being used.
-Clayton
On Tue, Sep 8, 2015 at 1:15 PM, John Skelton jskelton@lr.mercycorps.org wrote:
Hi CommCarers
I'm seeking clarity on whether the amount of case properties that you
have make a difference to the load that is placed on the mobile device
(even if these properties are not added to case detail or case list)? I am
interested, because for our app we want to overlay our basic activity
information with some in-depth baseline surveys. One option is to save each
of the survey questions (about 100) to case properties. This could help
with analysis later, particularly when comparing changes between baseline
and endline surveys as I can use case export for this. However, if it adds
burden to the phones then it's probably best to not add these to case data.
Is there a general rule of thumb about the appropriate maximum number of
case properties to be attached to each case?
Thanks!
John
--
You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "commcare-users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/commcare-users/PHBkyBOdiCc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
John Skelton
Results, Learning and Research Manager - Prospects Program
Mercy Corps Liberia
mobile: +231 880 964 479 | Skype: john.skelton99