Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have one legitiment complaint- Safari Doesn't Cache Pages
- Thread starter Simgar988
- Start date
- Sort by reaction score
Yeah, it's not a bug, just not enough RAM. However, this is version 1 software (well, parts of it anyway), so I am hopeful they can optimize the cacheing better. It is a shame they didn't just go for the 512 MB though, I think they were too obsessed with hitting that $500 price point and were counting every penny.
This is incorrect. While Safari will reload every time I hit the back button, I can have 5 simultaneous tabs open on different sites and switching back and forth works fine with no reloading, even on sites with a lot of images.
I too created a thread about this reloading issue with title "low RAM Issue" last week. some agreed with me while others said that they don't have this issue. I even went to Bestbuy, and ipad there had the same issue, especially if you have 4 pages loaded with heavy graphic, like engadge dot com.
This is very annoying. I end up have only one page open. what is the point of multi-page support?
This is very annoying. I end up have only one page open. what is the point of multi-page support?
What we are discussing in this thread is reloading when you hit the back button in one tab of Safari.
That's different than having multiple tabs. Again, when I tested it, I was able to load Engadget, Gizmodo, MacRumors, MSN, and Yahoo in separate tabs and have no reloading at all when jumping between them.
And yet, hitting the back button in one single tab causes a reload every time.
Caching a deal breaker
My 3G isn't here yet but if it did make cache files that might be a deal breaker 16GB being consumed by apps videos music books would fill up fast if safari cached each page, have you ever looked at just how big it is on you Mac? I would call it a feature not a deal breaker.
Just something for every one to consider.
My 3G isn't here yet but if it did make cache files that might be a deal breaker 16GB being consumed by apps videos music books would fill up fast if safari cached each page, have you ever looked at just how big it is on you Mac? I would call it a feature not a deal breaker.
Just something for every one to consider.
Not only that. That will definitely kill any chances of using limited 3G plan.
Are you sure they are using RAM as VRAM? Regardless, I'm sure this can be improved as it was on the iPhone.
One of the biggest problems with this is that you can't go back to dynamic sites without it reloading either.
For example, Google Reader. If you click an article to view it in original source in a new tab, and than close that source, it'll go back to the gReader tab and still reload the site, losing any dynamic content you had on that page. Since reloading will clear any viewed articles, I won't be able to share those viewed content. I'd have to view all items instead of unread items in order to do what I want to do.
For example, Google Reader. If you click an article to view it in original source in a new tab, and than close that source, it'll go back to the gReader tab and still reload the site, losing any dynamic content you had on that page. Since reloading will clear any viewed articles, I won't be able to share those viewed content. I'd have to view all items instead of unread items in order to do what I want to do.
Fully Aware of the difference
So I think we were using the word cache different in this case it wasn't clear in my statement but I was talking about cache files, from pages that are not active those files would be cached in RAM until the page file is needed to extend the RAM onto storage, and Unix must have a page file. Sorry for not being clear.
So I think we were using the word cache different in this case it wasn't clear in my statement but I was talking about cache files, from pages that are not active those files would be cached in RAM until the page file is needed to extend the RAM onto storage, and Unix must have a page file. Sorry for not being clear.
Cache Files
I was talking about cache files. As I was talking about files. I did not say RAM. It wasn't 100% clear.
I was talking about cache files. As I was talking about files. I did not say RAM. It wasn't 100% clear.
Mobile Safari caches only to available RAM, not to the limited write cycle flash memory.
Yahoo did a detailed analysis of how iPhone Safari caches (we can guess it wasn't changed for the iPad), and found this behavior:
The lack of cache when going backward to a visited page is a real pain at times, especially in forums. Even mobile IE usually acted better in this regard.
Yahoo did a detailed analysis of how iPhone Safari caches (we can guess it wasn't changed for the iPad), and found this behavior:
- Safari for iPhone will only cache files 25 KB or smaller served using the Expires explicit expiration time or Cache-Control max-age directive HTTP headers. Files without those headers will not be cached.
- Safari decodes the file before saving it to cache, meaning the total unzipped file size must squeeze under the 25 KB ceiling to hit the cache.
- Components already in cache are only replaced by new cacheable components using the least recently used algorithm.
- Safari for iPhone is able to cache a maximum of 19 external components, placing a maximum cache limit at around 475 KB.
The lack of cache when going backward to a visited page is a real pain at times, especially in forums. Even mobile IE usually acted better in this regard.
I noticed that when you leave one page for another if you dont return in a certain time span that page will need to refresh. Makes it tough to say load the Facebook chat session then browse another site, when you go back to the fb chat it just refreshes which effectively means your session was terminated.
Here is to hoping that opera releases an ipad optimized browser because the iphone browser is very sweet right now. Def some hiccups, but it should help with this issue a good deal I would think. Unless of course the system resources just aren't available for the opera browser to work the same on the ipad.
There are a couple of hiccups that will be fixed shortly (mostly with scrolling and no scroll lock when zoomed), but I would say that it is what safari should have been. I am pretty shocked at how quick it moves. I watched a video demo, in the time it took safari to load NYtimes site, opera loaded the main site and 4 other pages of full content. I used it and it indeed does work that quick.
The cache works great on this and going back to different pages works just like it should (no reloads). Safari needs to learn a few things from this. Again Opera should hopefully make an ipad optimized version of this. Would be truly great.
The cache works great on this and going back to different pages works just like it should (no reloads). Safari needs to learn a few things from this. Again Opera should hopefully make an ipad optimized version of this. Would be truly great.
If they did that would be great although I hate using browsers w/ out pinch to zoom