Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: Scaling java app Date: Fri, 2 Dec 2016 20:25:26 -0000 (UTC) Organization: A noiseless patient Spider Lines: 21 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Fri, 2 Dec 2016 20:25:26 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="866927060f36e5e571ddc817c7e8c3f6"; logging-data="13821"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18zW2ShTm2XnxsFro62pzHRkVm9DOZWGfQ=" User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT b8fc14e git.gnome.org/git/pan2) Cancel-Lock: sha1:AlR+cVJVPb1oTOWHbiSszzMqdVc= Xref: csiph.com comp.lang.java.programmer:36028 On Fri, 02 Dec 2016 15:05:30 -0500, Jerry Stuckle wrote: > RUNSTATS updates the current statistics on the database, and REBIND > rebinds all applications, creating new access plans for each. > You've got to be kidding! RUNSTATS is fine, but old fashioned: but something like REBIND was outdated by the mid 1990s: Even Sybase 10 didn't need any application rebinding malarky. By contrast PostgreSQL does all that invisibly and automatically and has been that way since I started using it around 2005. It updates statistics and tidies indexes periodically via internal threads. Execution plans are set up the first time a program runs each query, so are always current. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |