Re: Evaluating the performance of new features

Do we have actual evidence that indexeddb performance is a problem? I've never seen any. - Kyle On Feb 1, 2015 3:45 PM, "Fabrice Desré" wrote: > On Sat, 31 Jan 2015 20:05:46 +0800, Philip Chee wrote: > > > On 31/01/2015 14:03, Vladan Djeric wrote: > >> We do need a performant key-value store im

Re: Evaluating the performance of new features

Fabrice Desré wrote: On Sat, 31 Jan 2015 20:05:46 +0800, Philip Chee wrote: On 31/01/2015 14:03, Vladan Djeric wrote: We do need a performant key-value store implementation. This has been discussed before and various people have come up with proposals (myself included), but no one has had the

Re: Evaluating the performance of new features

Vladan Djeric wrote: - Also be careful about using SQLite Definitely good advice. SQL is way overkill for most common storage needs. A Key/Value engine may be too simple, at the opposite extreme.

Current recovery plan for gecko-dev and git (Was: Re: gecko-dev and Git replication will be broken for a little while)

Here is an update on our plans and status. = Overview = gps and hwine will implement the plan, which is, in summary, manually playing back the problematic merges one by one to ensure both systems are in agreement. gps has point and hwine is online for peer review of the work. No further tree clo

Re: Current recovery plan for gecko-dev and git (Was: Re: gecko-dev and Git replication will be broken for a little while)

5pm PST update: Work is progressing smoothly. We are currently at step 8 in the detailed plan posted earlier. That is, all commits have been manually processed and the head of both systems matches. We'll send an update when work is complete, or at 9am PST, whichever is sooner. Best, Laura On S

Re: gecko-dev and Git replication will be broken for a little while

GitHub syncing has been restored. Replication on git.mozilla.org is still recovering. But we're over the big hump (getting the two systems to agree on SHA-1s). On Fri, Jan 30, 2015 at 5:01 PM, Gregory Szorc wrote: > I figured people would like an update. > > There were multiple, independent fai

Re: Current recovery plan for gecko-dev and git (Was: Re: gecko-dev and Git replication will be broken for a little while)

7.30 PST update: Work is largely complete (with two exceptions, and no force pushes required) and we are currently re-enabling automation. We have left gecko-projects and integration/gecko-dev for now and will pick these up in the morning. Thank you for your patience while the team worked through

Re: Evaluating the performance of new features

On Sun, Feb 1, 2015 at 3:28 AM, Kyle Huey wrote: > Do we have actual evidence that indexeddb performance is a problem? I've > never seen any. Yup. I think this is a very good question. Did the people writing https://wiki.mozilla.org/Performance/Avoid_SQLite_In_Your_Next_Firefox_Feature gather a

Re: Evaluating the performance of new features

On Sun, Feb 1, 2015, at 11:13 PM, Jonas Sicking wrote: > On Sun, Feb 1, 2015 at 3:28 AM, Kyle Huey wrote: > > Do we have actual evidence that indexeddb performance is a problem? I've > > never seen any. > > Yup. I think this is a very good question. > > Did the people writing > https://wiki.moz