<div dir="ltr"><div>I must admit James that I have don't know for sure how performance could be measured and I have been trying to find proper way to measure it.<br>One thing I know for sure however is that measurement units are supposed to be standardized and rarely change <a href="https://en.wikipedia.org/wiki/Computer_performance">https://en.wikipedia.org/wiki/Computer_performance</a>.<br>The problem either way would to turn whatever performance unit given into a unit of time given the size of the data set before starting the training process, and this is my point of research at the moment.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 28 Mar 2019 at 10:01, James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks. Are there standard measures of hardware performance you could<br>
use as estimates? Measurement units change over time. At the moment<br>
I'm most familiar with Geekbench multi-core processor scores.<br>
<br>
On Thu, Mar 28, 2019 at 09:09:53AM +0200, Ahmed ElSabbagh wrote:<br>
> As for hardware, I am not sure how strong should it be to run a training model<br>
> for Neural Network or any other classifier.<br>
> <br>
> As for internet access, the training can be done offline no problem, it can be<br>
> slow depending on the size of the data set they add, it could be a feature to<br>
> try predict or estimate the amount of time it will take them given a minimum<br>
> hardware specification, the problem however will be the lack of pictures to<br>
> use, so a minimum number of photos and categories can be provided offline at<br>
> any given time, with other pictures and categories available downloadable<br>
> whenever internet is available.<br>
> <br>
> On Thu, 28 Mar 2019 at 02:41, James Cameron <[1]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote:<br>
> <br>
> Godo discussion, thanks.<br>
> <br>
> In addition to hardware limits, also try to avoid requiring internet<br>
> access.<br>
> <br>
> --<br>
> James Cameron<br>
> [2]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> _______________________________________________<br>
> Sugar-devel mailing list<br>
> [3]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [4]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> <br>
> References:<br>
> <br>
> [1] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [2] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [3] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [4] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
-- <br>
James Cameron<br>
<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div></div>