Do we need this criteria? RAM - Does it hurt to move an instance that has <4GB? NPAPI - We've announced that we'll remove support this year [1]. Should we just wait until we do? Do we have a solution for Flash on Win64 that makes this viable?
Lawrence [1] https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ On Thu, May 12, 2016 at 3:12 PM, Ben Hearsum <bhear...@mozilla.com> wrote: > This is a slight change from the current model where we purposely make the > client very dumb, and make the decision on the server (to minimize the > possibility of client-side bug making updates impossible). However, this > doesn't seem like a case where we could get somebody stuck very easily, and > I don't see a practical way of making the decision on the server if it > requires this much information. > > On 2016-05-12 01:07 PM, Ted Mielczarek wrote: > >> I suspect we'd want to add some extra token like "it's ok to update this >> 32-bit build to a 64-bit build", and have all the gating logic live on >> the client-side. Odds are if we want to change the criteria we'd have to >> change the client anyway. >> >> -Ted >> >> On Thu, May 12, 2016, at 12:56 PM, Ben Hearsum wrote: >> >>> Do you have thoughts on how we'll be able to serve the users the correct >>> build if we have to base the decision on plugins they may have or other >>> information that's not in the update ping? We can already detect 32-bit >>> builds on 64-bit Windows through the build target, but information about >>> plugins or RAM is not something we know about when serving updates. >>> >>> On 2016-05-12 11:45 AM, Ted Mielczarek wrote: >>> >>>> Hello, >>>> >>>> Given all the discussion around SSE[2] lately, I was curious as to >>>> whether we had made any plans to update Windows users that are running >>>> 32-bit Windows builds on a 64-bit Windows OS to our 64-bit Windows >>>> builds. The 64-bit Windows builds do use SSE2, since that's a baseline >>>> requirement for x86-64 processors, and the overall performance should >>>> generally be better (modulo memory usage, I'm not sure if we have an >>>> exact comparison). Additionally 64-bit builds are much less likely to >>>> encounter OOM crashes due to address space fragmentation since they have >>>> a very large address space compared to the maximum 4GB available to the >>>> 32-bit builds. >>>> >>>> It does seem like we'd need some minimal checking here, obviously first >>>> for whether the user is running 64-bit Windows, but also possibly >>>> whether they use 32-bit plugins (until such time as we unsupport NPAPI). >>>> 32-bit plugins will not work on a 64-bit Windows Firefox (we do not have >>>> the equivalent of Universal binaries like we do on OS X). >>>> >>>> -Ted >>>> >>>> >>> _______________________________________________ >>> dev-platform mailing list >>> dev-platform@lists.mozilla.org >>> https://lists.mozilla.org/listinfo/dev-platform >>> >> > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
