LISTSERV mailing list manager LISTSERV 16.5

Help for QSERV-L Archives


QSERV-L Archives

QSERV-L Archives


QSERV-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

QSERV-L Home

QSERV-L Home

QSERV-L  September 2013

QSERV-L September 2013

Subject:

notes from qserv mtg (Sept 19)

From:

Jacek Becla <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Tue, 24 Sep 2013 13:02:13 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (66 lines)

Attendees: Serge, Douglas, Bill, Jacek

300 node test
  - "select from obj join source using objectId where objectId = <xx>"
     results in full scan, objectId index not recognized, probably
     subchunks materialized too. Code needs to be fixed
  - still some issues with getting cluster correctly configured
    for smaller # nodes
  - need to run few low-volume queries (eg "select from source
    in a very small region")
  - run near neighbor for 10x10 deg
  - returning the nodes ~Sept 24

bugs
  - worker still hosed under some conditions, writing/reading
    results is synchronized incorrectly: results are read
    before they are populated
  - some bugs Bill found are handled through fault tolerance,
    code not yet merged to master


logging
  - Bill wrote some code for logging, thread safe,
    outputs buffers one full line at a time, with thread
    id and time stamp
  - using boost filtered strings, not using any package
    like logcxx
  - it will be easy to migrate once we settle on the package
    we should use long term


what is next (not - till the construction starts)
  - high priority: finalize documentation or FDR
  - then: code refactoring


Qserv code refactoring between now and start of
the Construction - two options:
  a) bottom up (start from the existing prototype
     and cleanup/fix/tweak/improve)
       or
  b) top down (come up with a fresh clean design based
     on all lessons learned, reuse pieces from the existing
     prototype)
  - overall sentiment based on very preliminary discussion
    (without Daniel!): "b"
  - main reason: existing prototype has too many layers,
    very hard to debug
  - other points made:
   - would be good to implement geometry support
     in c++, not from python
   - would be good to get rid of subchunks
   - would be good to push more code from python to C++
  - also... want to switch to the MariaDb distribution

The topic of code refactoring will be discussed
in details in the next few weeks...

Jacek

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2018
February 2018
January 2018
December 2017
August 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use