Atom feedLast 5 comments
37 years ago
Ray: Having the same problem. Very frustrating. Luckily, for some reason my released version worked on the iPad itself, but now I can't get it to run in the simulator. Getting no such table, which I'm guessing is an initialization error. Will continue to investigate.
Ray: Having the same problem. Very frustrating. Luckily, for some reason my released version worked on the iPad itself, but now I can't get it to run in the simulator. Getting no such table, which I'm guessing is an initialization error. Will continue to investigate.
38 years ago
Jeremy: FYI, I've just tried it with the SQLite 3.7.0 preview and the same problem occurs.
Also, I'm not using any extra third-party libraries with my SQLite, so the problem isn't your Unicode extension.
Jeremy: FYI, I've just tried it with the SQLite 3.7.0 preview and the same problem occurs.
Also, I'm not using any extra third-party libraries with my SQLite, so the problem isn't your Unicode extension.
38 years ago
Jeremy: I'm having the same problem with compiling SQLite against iOS 4 for the iPad simulator, but in my case it works fine running on an actual iPad (also works in the iPhone simulator and on an iPod Touch).
Same problem with 3.6.23.1, 3.6.23, and at least back to 3.6.21. Compiling against iOS 3.2 makes it work, though that's not really an option for iPhone (as opposed to iPad) apps.
I have no idea what to do about it or how big a problem it really is...
Jeremy: I'm having the same problem with compiling SQLite against iOS 4 for the iPad simulator, but in my case it works fine running on an actual iPad (also works in the iPhone simulator and on an iPod Touch).
Same problem with 3.6.23.1, 3.6.23, and at least back to 3.6.21. Compiling against iOS 3.2 makes it work, though that's not really an option for iPhone (as opposed to iPad) apps.
I have no idea what to do about it or how big a problem it really is...
38 years ago
Pascal: The problem seems to have deep roots, however there is a solution, see the updated post. :)
Pascal: The problem seems to have deep roots, however there is a solution, see the updated post. :)
The archive
March 2011 (1)
July 2010 (1)
October 2009 (2)
August 2009 (1)
July 2009 (1)
March 2009 (1)
December 2008 (1)
October 2008 (1)
August 2008 (1)
July 2008 (3)
June 2008 (1)
May 2008 (3)
March 2008 (1)
February 2008 (3)
January 2008 (2)
November 2007 (1)
October 2007 (1)
September 2007 (1)
August 2007 (1)
July 2007 (1)
June 2007 (3)
May 2007 (1)
April 2007 (1)
February 2007 (2)
January 2007 (3)
December 2006 (1)
November 2006 (3)
October 2006 (2)
September 2006 (2)
August 2006 (1)
July 2006 (2)
June 2006 (6)
iPhone JavaScript Benchmark (kind of)
Saturday, July 21th 2007 - 18:53
I offered Andrew Yee to bring his great medical eponym database to the iPhone and therefore started working on an iPhone client. Due to the lack of an iPhone I am only testing this client on my MacBook Pro and Safari/iPhoney, but the iPhone is not as powerful as my laptop, surprise surprise.
So to be able to determine what the iPhone is capable of, I let the client spit out some debug information - and this gives a good opportunity to compare or even benchmark iPhones' Safari to Safari on other platforms (or other browsers). Of course this is not a complete benchmark, nevertheless it's interesting to see how iPhones' Safari performs on three tasks:
In case you want to send me your results, load the following URI in Safari or iPhoney, hit "Load eponyms..." and tell me what gets written on the leftmost page:
code.hillrippers.ch/eponyms/
Here is what I have so far, if not specified otherwise Safari 3 Beta on OS X (10.4.10) was used:
* plus displaying a warning that the script does not respond
What impressed me most is the blatant difference between the iPhone and my old G4 Mac. It is waaay slower than the iPhone on certain tasks. If anyone has a more recent G4 Mac I'd very much like to see how it performs, Safari 3 values preferably.
The page won't render 100% correctly on other browsers (there'll be a seperate version for the desktop FYI).
So to be able to determine what the iPhone is capable of, I let the client spit out some debug information - and this gives a good opportunity to compare or even benchmark iPhones' Safari to Safari on other platforms (or other browsers). Of course this is not a complete benchmark, nevertheless it's interesting to see how iPhones' Safari performs on three tasks:
- generating ~1'600 JavaScript objects
- adding ~1600 links to a div (DOM)
- animating two div transitions
In case you want to send me your results, load the following URI in Safari or iPhoney, hit "Load eponyms..." and tell me what gets written on the leftmost page:
code.hillrippers.ch/eponyms/
Here is what I have so far, if not specified otherwise Safari 3 Beta on OS X (10.4.10) was used:
| Device | download (AJAX) | generating objects | adding links | animation |
|---|---|---|---|---|
| iPhone | 8'500 ms | 550 ms | 185 ms | 13 - 20 fps |
| MBP 2.33GHz, 2GB RAM | 500 ms | 370 ms | 98 ms | 83 - 100 fps |
| MBP + Camino 1.6a | 170 ms | 1234 ms | 320 ms | 23 - 30 fps |
| MBP + Firefox 2.0.0.4 | 440 ms | 1450 ms | 320 ms | 23 - 30 fps |
| PM G4 350MHz, 704MB RAM | 1'500 ms | 3'800 ms | 1'500 ms | 13 - 17 fps |
| PM G4 + Safari 2 | 1'750 ms | 7'150 ms | 1'440 ms | 17 - 20 fps |
| PM G4 + Camino 1.6a | 750 ms | 16'550 ms * | 3'200 ms | 7 - 10 fps |
What impressed me most is the blatant difference between the iPhone and my old G4 Mac. It is waaay slower than the iPhone on certain tasks. If anyone has a more recent G4 Mac I'd very much like to see how it performs, Safari 3 values preferably.
The page won't render 100% correctly on other browsers (there'll be a seperate version for the desktop FYI).
Naig at 07.08.2007 19:48
He he, was du amigs am samschtig abig so machsch :-)
He he, was du amigs am samschtig abig so machsch :-)
Comments are disabled
Rafael: Thank you very much, I was having a huge headache to solve the very same problem!