Rob, Sorry if I've wasted anyones time looking into what appeared initially to be a viking problem.
Having experimented a little more I now know that viking is not responsible for my laptop crashing - it has now crashed several times using other programmes only, and it's problems don't seem to be related to the 'load'. The screen does not dim when it crashes. The screen remains showing whatever I was working on, & the keyboard & mouse become unresponsive - it does not recover from this no matter how long it is left. Not a viking problem. In terms of the screen dimming when loading a number of tracks at once, this is only a minor problem for me as the laptop always recovers (except sometimes in my case when using the defective laptop!). Regards Nick On 13/01/12 02:39, Robert Norris wrote: >> >> All my tracks, hiking, car& cycle, are 1 second interval,& I >> frequently deal with multiple tracks created during the course of a >> days cycling or walking. >> >> The majority of my tracks are created by a Garmin Oregon 300. When I >> load the tracks (generally using file / append) my laptop screen dims& >> everything freezes for several seconds, but always recovers. If there > After loading each individual gpx file, Viking generates a redraw at the view > to see all of that gpx. > > This means if there's a map layer present it will load/download tiles > for that view too (reading lots map tiles from disk times a little time) > > > > At present it's not clever enough to only do the redraw when the last gpx is > opened. > > > > This should be simple to generate the code improvement. > > > >> are several tracks with many waypoints the programme may become slower > ^^^^^^^^^^ > > Using many waypoints* will slow Viking down as it's written using the > traditional (i.e. slow Gdk API graphics functions)**. > > > But there is a workaround by adjusting the TrackWaypoint Layer Properties, > Waypoints tab: > > > > 1. Turn off 'Draw Labels' > > - This seems to make the biggest difference as drawing text to the viewport > is slow (especially when panning the screen around) > > > > 2. Turn off 'Draw Waypoint Symbols'*** > > > > > > * Interestingly only just discovered this - helped by using some 1000 > Waypoint gpxs. > > I use Viking with massive tracklogs, so I don't really notice this issue. > Behaviour is worse on my laptop then the desktop, presumably since the laptop > is of a lower spec. > > > > ** Rewriting Viking to use cairo / champlain for the main view is a > possibility .... but don't hold your breath for this little volunteer > project. > > > > *** There might be a way for this to scale up better, however the main > slow down is in point 1, so IMHO there's not much incentive to attempt > to address this. > >> but still functions. However, I need to save the file at an early >> stage, and then keep saving at regular intervals as I edit the tracks, >> combining them, removing duplicates, and uploading them to OSM etc. If >> I don't regularly save the whole laptop will freeze and not recover, >> necessitating holding the power button for a few seconds to switch it >> off, and then starting again. I don't have evidence of this, but >> creating a track/route seems to use even more resources, so my laptop >> may crash more often - again frequent saving stops this. > The whole laptop freezing seems a symptom of allocation vast amounts of > memory and the system locks up. Eventually the OOM Killer may kick in a > removes a lucky program. I don't think there are any severe memory leaks or > memory allocations in Viking (other then DEMs) .... > > The only cause I know of in Viking is opening *lots* of DEMs (i.e. over 50 or > more). > Redrawing with DEMs is also very slow as they recalculate every point on > display. > For using DEMs (this is how I do it:), is to load them in for your area - my > machine copes with coverage of the UK for example *but keep the layer > invisible*. > Since you probably have OSM tiles for map view anyway, the DEMs don't need to > be visible but they'll still be used the other DEM functionality: the cursor > height readout, track creation and track property elevation display. > > >> It may be that a feature that regularly saves to disk at 2 minute >> intervals would alleviate this? > This maybe something to add. > >> I hasten to add, this is not a complaint - you asked, so I'm answering. >> I'm a long term fan of viking& recommend it to friends. I also think >> that Ubuntu may be partially to blame here, as the performance of the >> laptops seems to have reduced over the last 2 versions of Ubuntu. It's >> difficult for me to say if other programmes can cause similar effects, >> but I do know that 'Evolution' the PIM programme is resource heavy and >> can slow my system causing similar problems. I think the problems >> partially depend on the other programmes running - Thunderbird causes >> less problems than Evolution, Chromium causes less problems than >> Firefox. > I'm glad you're a fan. > >> My computer is a laptop, Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz with >> 4GB of ram, running Ubuntu 11.10 (can also boot into windows 7, where >> there is a version of Viking as well, but I rarely do this& don't know > Your laptop seems well specc'ed especially with 4GB RAM. > > NB All my machines are single core efforts. > I wouldn't have thought multi core machines would effect Viking negatively. > May be you could try on a single core machine and see how that compares? > > Rob. (OSM user robbieonsea) > ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
