Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.022 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'subject:Python': 0.06; '128': 0.09; '22,': 0.09; 'indeed,': 0.09; 'changes': 0.15; '23,': 0.16; '384': 0.16; 'fits': 0.16; 'gig.': 0.16; 'objects.': 0.16; 'objects?': 0.16; 'received:mac.com': 0.16; 'roy': 0.16; 'slow,': 0.16; 'subject:ORM': 0.16; 'subject:library': 0.16; 'wrote:': 0.18; 'hacking': 0.19; 'received:10.0.1': 0.19; 'fit': 0.20; 'memory': 0.22; 'cc:addr:gmail.com': 0.22; 'cc:2**1': 0.23; 'diverse': 0.24; 'tend': 0.24; 'cc:no real name:2**0': 0.24; 'idea': 0.28; 'am,': 0.29; 'scale': 0.29; 'related': 0.29; 'url:mailman': 0.30; 'second,': 0.31; 'url:python': 0.33; 'could': 0.34; 'problem.': 0.35; 'objects': 0.35; 'but': 0.35; 'acceptable': 0.36; 'url:listinfo': 0.36; 'subject:?': 0.36; 'received:10.0': 0.36; 'url:org': 0.36; 'too': 0.37; 'received:10': 0.37; 'being': 0.38; 'server': 0.38; 'received:17': 0.38; 'to:addr:python-list': 0.38; 'sure': 0.39; 'to:addr:python.org': 0.39; 'url:mail': 0.40; 'how': 0.40; 'days': 0.60; 'even': 0.60; 'email addr:gmail.com': 0.63; 'more': 0.64; 'total': 0.65; 'charset:windows-1252': 0.65; 'smith': 0.68; 'default': 0.69; '2014,': 0.84; 'header:In-reply-to:1': 0.84; 'subject:read': 0.84; 'quantitative': 0.91; 'lot,': 0.93 MIME-version: 1.0 Content-type: text/plain; charset=windows-1252 Subject: Re: Python ORM library for distributed mostly-read-only objects? From: William Ray Wing In-reply-to: Date: Mon, 23 Jun 2014 09:43:53 -0400 Content-transfer-encoding: quoted-printable References: <85659fdd-511b-4aea-9c4b-17a4bbb88662@googlegroups.com> To: python-list@python.org X-Mailer: Apple Mail (2.1878.2) X-MANTSH: 1TEIXREEbG1oaGkdHB0lGUkdDRl5PWBoaGBEKTEMXGx0EGx8SBBscHwQdGBAbHho fGhEKWE0XSxEKbX4XGhEKTFkXGxobGxEKWUkXEQpZXhdjbnkRCkNOF0sbGBpiTk0ZBB1/chl4c wcfZBsZHhlfHREKRUMXFmhpHR4abx8fB2sZH2gHHm8aGQdoHRkbBx4fbm8ZaBgbaxIeb2pHS0k ESUVHFBEKWFwXGQQaBBseB01OHBMaGh0TBRsdBBsfEgQbHB8EHRgQGx4aHxsRCl5ZF2EZTmUZE QpMRhdsa2sRCkNaFx8aBBseHQQcHgQYGxEKRFgXGREKREkXGBEKQkUXa0QFel5TTWVGeXgRCkJ OF2hGQkAfSHkdRx9kEQpCTBdienoab1ATZ1BZWREKQmwXZGRmc25YR0hlfUYRCkJAF24FXmVYG nsfY0t9EQpwaBdvX2JgSHh6BQFhYhEKcGgXbh14GRpyYn5Hf3IRCnBoF21gE0V8blpoYmJJEQp waBdoTVhGf05mchxyXxEKcGgXbRpcUB14XHpbRhIRCnB/F2NFRxtTUkNvYhlzEQpwXxdoTGEaR kdsR0xTaBEKcGwXbm4STxxjeGBnUmUR X-CLX-Spam: false X-CLX-Score: 1011 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.14,0.0.0000 definitions=2014-06-23_07:2014-06-23,2014-06-23,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1406230151 Cc: smurfix@gmail.com, "William R. Wing" X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 31 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1403534666 news.xs4all.nl 2880 [2001:888:2000:d::a6]:40872 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:73514 On Jun 23, 2014, at 12:26 AM, smurfix@gmail.com wrote: > On Sunday, June 22, 2014 3:49:53 PM UTC+2, Roy Smith wrote: >=20 >> Can you give us some more quantitative idea of your requirements? = How=20 >> many objects? How much total data is being stored? How many queries=20= >> per second, and what is the acceptable latency for a query? >=20 > Not yet, A whole lot, More than fits in memory, That depends. >=20 > To explain. The data is a network of diverse related objects. I can = keep the most-used objects in memory but not all of them. Indeed, I = _need_ to keep them, otherwise this will be too slow, even when using = Mongo instead of SQLAlchemy. Which objects are "most-used" changes over = time. >=20 Are you sure it won=92t fit in memory? Default server memory configs = these days tend to start at 128 Gig, and scale to 256 or 384 Gig. -Bill > I could work with MongoEngine by judicious hacking (augment = DocumentField dereferencing with a local cache), but that leaves the = update problem. > --=20 > https://mail.python.org/mailman/listinfo/python-list