[GitHub] madlib issue #276: Feature/dev check
Github user asfgit commented on the issue: https://github.com/apache/madlib/pull/276 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/madlib-pr-build/520/ ---
[GitHub] madlib issue #276: Feature/dev check
Github user asfgit commented on the issue: https://github.com/apache/madlib/pull/276 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/madlib-pr-build/518/ ---
[GitHub] madlib issue #276: Feature/dev check
Github user asfgit commented on the issue: https://github.com/apache/madlib/pull/276 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/madlib-pr-build/517/ ---
[GitHub] madlib issue #276: Feature/dev check
Github user njayaram2 commented on the issue: https://github.com/apache/madlib/pull/276 Thank you for the comments @iyerr3 , will make the changes you have requested. Having one IC file for each module makes sense, but on Greenplum, for some modules the IC run time is still quite high. For example, if a module had 5 IC files, where each ran for 10 seconds, the user would see IC progressing every 10 seconds. But if those were combined into one IC file, the progression would happen after 50 seconds. It seemed a little odd (longer IC run times for some modules in terms of user experience) when we were trying it out, so decided to keep multiple IC files for such modules. ---