[
https://issues.apache.org/jira/browse/MADLIB-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120552#comment-16120552
]
ASF GitHub Bot commented on MADLIB-1118:
----------------------------------------
Github user edespino commented on the issue:
https://github.com/apache/incubator-madlib/pull/163
For future reference, this is how I reviewed the elastic_net install-check
execution:
* Update the following file:`<local git
repo>/src/ports/postgres/modules/elastic_net/test/elastic_net_install_check.sql_in`
* Added `\timing` to top of the file.
* Added `SELECT ASSERT (FALSE, 'Deliberately forced failure');` to the
bottom of the file to force a failure condition. This will allowed me to review
the timing information in the log files from the test execution.
* From build directory run `make install` to push updated install-check
file to installation directory
* Run only the elastic_net test suite (using Postgres):
`/usr/local/madlib/bin/madpack -s madlib -p postgres install-check -t
elastic_net
I updated the elastic_net_train tolerance values with varying values and
reran the repeated the scenario reviewing the recorded `Time:` values.
> Reduce size of elastic net install check table
> ----------------------------------------------
>
> Key: MADLIB-1118
> URL: https://issues.apache.org/jira/browse/MADLIB-1118
> Project: Apache MADlib
> Issue Type: Task
> Components: Module: Regularized Regression
> Reporter: Frank McQuillan
> Assignee: Ed Espino
> Priority: Minor
> Fix For: v1.12
>
>
> IC is taking too long for elastic net. I would suggest we reduce the size of
> the input data table.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
