Page History

Close issue 

Current Sprint - Sprint 24 ( February 18, 2016 – April 02, 2016 )

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint24

We have finished up phase 4 - lucene development (100% junits passing)

Upcoming Sprint:

Sprint 25 (March 03, 2016 – March 16, 2016)

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint25

Focus on performance.

Verify Remote API, CTS2, Browser, GUI.

Loader related issues:

After reviewing the existing OWL2 issues, Scott suggested that NCI reload the OWL2 files using the preference file and then re-test.

Lucene 6.4 performance

• Update from Scott

Scott gave an overview of 6.4 Lucene performance and how it compares to 6.3.  After implementing the Lucene hit collector and providing a cache, the performance appears acceptable.

There is still some tuning that needs to done to increase the performance.

Comparing performance from 6.4 to 6.3, some areas are better and some are a bit slower.

Larry was suggesting that we used the hit collector (that retrieved all of the results up front) to ensure we got the best results. Larry was wondering if we still need to retrieve all of the results up front.

Scott mentioned that collecting all of the results up front takes a large amount of time.

Larry suggested that we investigate the possibility of only returning an initial amount of results (for example 1000).

Scott reviewed the results spreadsheet.

Scott noted that the tree extension calls take longer.

Larry mentioned that that NCI would like to test it out and see how it performs.

OBI/OWL2 Load Issues

• Update from Gilberto

This was discussed during the prior meeting.

NCI acknowledged that they need to reload OWL2 with the preference file.

Gilberto will recheck his list of issues against this new load.

OBO Hierarchy Load Issues

• Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1671

VPN and GFE

• Update from Gilberto

Girlberto stated the request when up the ladder for approval.

Our RSA software token is tied to the user, not the machine.

RRF Loads

• • Updates if needed

Scott was wondering or the SMQs, can these be summarized in LexEVS?

Brian suggested that what the loader is doing is fine. 

He also suggested that in the browser, qualifiers - don't show on the browser.

Brian will come up with some examples to send out to the group to explore.

Scott will also send out his list of ten offenders that show this issue.

lexgrid.org xsd references