Ignoring the fact that browsers suck and Macs have poor cooling systems...
Roger that, and I appreciate the tip regarding FF's performance problem and Chrome being better. I got onto FF quit awhile ago, and all the benefits have been met or overtaken by other browsers. My problem with Google is their massive UNREPORTED income, which normally is a crime for a public company, they get from Uncle Sam to help the stupid and dangerous tracking of everyone's communications. Prior to Edward Snowden, a statement like that was speculative, now, it's only impolite. It's truth is unmistakable even if it can be denied, due to awkwardness of bringing it up. The money is unreported, because the anti-terrorists laws make it a crime to disclose when Uncle Sam makes an offer that cannot be refused to help him eaves drop, an offer made quite palatable by the fact that payment is with a blank check signed by the government handed over to the company to justify in terms that are not exposed to public scrutiny. 1% of that momey invested in Xenforo would do the world wonders. Come to think of it, I would be a little surprised if security services did not have their hands in XF's pants at least a little. May they get everything you could give them already, through their copy of all internet traffic they stream into their data centers, where back door keys to rsa and ssl encryption are ready to do their work. It's how Google pays for all that unlimited disk space, how generous it seem for them to do that, until we had proof of why they do it of them. The relevance here is I am loathe to support them by using their browser. But maybe I will relent
Politics Aside, Why Is the Import So SLOW?
But FF and Mac tech issues don't explain the why the the browser needs to pull any power for a job happening on a server. Ajax can send a progress update every five seconds and he load is next to nothing. Someday, I am going to find where that power is being wasted, because surely it is being wasted, right? The data conversion is not sending all the data to my mac. All the work is on the server so the PC doesn't need to be loaded more than with small ajax updates. Here is my guess. Updates to the PC are too frequent. The easy fix would be to make it configurable. That is only a guess, so until I have proof, I won't give words to my belief that this is a bug in the importer.
One more thing I am going to find out and if someone can just tell me, that would be great. Why does this import run slower pulling a brick factory's lorry up a hill? I am not trying to give nyone a hard time, but seriously, this things runs like 0.1% 0.2% progress increments for a long.or alonggggggggggg time. come back in an hour. So while it teams with FF to wreck my PC by pulling too power, it doesn't even go fast when it takes all that power.
As a reference, when we ported into phpbb3 this time last year, the scripts took awhile to write, but when they ran, they did 90% the volume we have now, and those scripts were done in less than 20 seconds. Unless the volume of data in hundreds of millions of records, there is never a reason for a conversion to take more than a few minutes. So what is up with that?
Please tell me the bottleneck is not sending a copy of the data to uncle sam and he has to get his copy before we get our conversion.