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  July 2014

QSERV-L July 2014

Subject:

Re: notes from Dev hangout July 2, 2014

From:

Kian-Tat Lim <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Wed, 2 Jul 2014 17:00:39 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

Daniel,

> Non-internet installation (DM-602), blocked because Anaconda
> python install script needs internet.
> [...]
> Anaconda: need LSST-approved/supported way of installing w/o
> internet. See:
> https://dev.lsstcorp.org/cgit/LSST/external/anaconda.git/tree/ups/eupspkg.cfg.sh
> 
> Suggest requiring all eups dependencies installable by only
> touching the eups distributions server (i.e., not continuum.io
> <http://continuum.io> server)

	Anaconda is not supposed to be a stack dependency.  The idea is
that the LSST Stack works with whatever Python (plus numpy) you have
installed.  We offer to install Anaconda as a convenience, not a
requirement.  In this way, Python is similar to a system package (like
bison).

> eups packaging and distribution:
> One problem: no way to share permissions so that multiple people can
> use the eups distribution tool to manage distribution
> packages. Suggest a shared account (e.g., qservsw) that the devs can
> share. Perhaps use a sudo-like system so that each dev can run eups
> commands as that user.

	Ideally management of packages on a distribution server should
be automated and not manual.

	Note that sharing a stack installation is normal and can be done
using group permissions.

> mysql result plumbing: Creating custom local_infile handler in
> mysqlclient seems to be the fastest way to get in-process data through
> a mysqlclient into a mysql table. Other options: "prepared" insert
> statements with binding parameters; writing directly into
> myisam. Prepared statements are probably slower--mysql doc "8.3.2.1
> Speed of INSERT Statements" suggests that LOAD DATA INFILE is the
> fastest way to bulk-load data.

	Prepared statements are likely slower, but it's not clear by how
much.  They may be sufficiently performant, and are much easier to
support.

-- 
Kian-Tat Lim, LSST Data Management, [log in to unmask]

########################################################################
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