Re: [R-SIG-Mac] Poor plotting performance on Mac OS X

2017-08-02 Thread David Winsemius
> On Jul 6, 2017, at 4:12 AM, Ashley Betts > wrote: > > Hi All, >I'm quite new to R and recently started investigating the geospatial > plotting capabilities of R via ggplot2. I started by using some of the > publicly available datasets from the

Re: [R-SIG-Mac] Poor plotting performance on Mac OS X

2017-07-10 Thread peter dalgaard
Thanks Don, Can you perhaps make that a little closer to being reproducible for people who might want to try it on newer hardware? (packages, location of input file). (And by the way, xterm? What did Terminal.app do to you?) This, along with a thread from 2014 that Google dug up, strongly

Re: [R-SIG-Mac] Poor plotting performance on Mac OS X

2017-07-10 Thread MacQueen, Don
For what it's worth, here is my experience on a late 2013 Mac Pro. (I normally run R from an xterm shell within an X Windows context) The best performance for displaying the image on-screen uses cairographics and Polypath. It's the only one fast enough to be satisfactory for interactive use, in

Re: [R-SIG-Mac] Poor plotting performance on Mac OS X

2017-07-10 Thread Ashley Betts
Hi Peter, outputting to PDF made a huge difference! It ran for only 15 seconds and there was no trailing unresponsive prompt. The PDF ended up being around 2Mb and opened and displayed almost immediately in Preview. I did watch the system when I was outputting to the quartz device last time and

Re: [R-SIG-Mac] Poor plotting performance on Mac OS X

2017-07-10 Thread peter dalgaard
Pretty clear that the process is getting stuck in Apple-graphics land, then. This could be inefficiency of the device driver, but also just ... Apple. Could you try running the same thing to a PDF (AFAIR, just open the device with pdf(file="myplot.pdf"), then print(plt), then dev.off()). It

Re: [R-SIG-Mac] Poor plotting performance on Mac OS X

2017-07-09 Thread Ashley Betts
Oh yes, sorry about that. I originally had screen shots attached showing the timings but the email ended up being too large. All of the time is in the print. Nearly all other commands run within seconds. Oddly, after approximately half hour the prompt returns which I get one Sys.time() to

Re: [R-SIG-Mac] Poor plotting performance on Mac OS X

2017-07-09 Thread peter dalgaard
Hmm, you're not telling us much about where the time is being spent. Some more detailed timing using system.time() could be useful. If it is a graphics device issue, I would expect almost everything in the final print(plt). You could try switching graphics device, e.g. to pdf() which should be