On 15 August 2013 19:27, Miguel de Benito Delgado < m.debenito.delg...@gmail.com> wrote:
> On Wed, Aug 14, 2013 at 11:28 AM, Michael Lachmann <lachm...@eva.mpg.de>wrote: > >> One needs to think about when/how to clean the cache. > > > Yes, this is definitely the issue. But do we really need persistent > storage? > Well, there was a period when TeXmacs had some problem and was drawing some images really slowly. Then it helped a lot. When you opened a file with lots of images, and wanted to get to the bottom, or look for a particular part. These days images draw qiote fast, but when looking at some files, it is still a bit annoying. Look for example here: https://www.dropbox.com/s/u4r5i8hmqc8v2zn/technical_replicates.tm Then imagine a file with 100 such images... > Think also, that some people run several instances of TeXmacs at the same > time (I hear libelous claims that TeXmacs crashes occasionally when several > windows are open ;) and this may complicate things further (although > admittedly, this multiple instance issue isn't addressed at all elsewhere). > > Because it is cached by CRC, I don't think it should be a problem, unless people are opening the same file at the same time twice, and an image is not cached, yet. But one could create the image and move it to its location at the last moment, and then there should be no issue. > Why not change that "false" to "true" in the call to cached_load_picture() > inside scalable_image_rep::draw()? No sweating but a great performance win. > Unless there's some hidden issue, of course. > -- > I noticed that when I open the file above, close it, and open it again, images load fast, which seems to imply that there is already some cacheing going on, as long as you don't quit TeXmacs. Michael
_______________________________________________ Texmacs-dev mailing list Texmacs-dev@gnu.org https://lists.gnu.org/mailman/listinfo/texmacs-dev
