| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Alexandru Coseru <alexandru(dot)coseru(at)totaltelecom(dot)ro> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Regex performance issue |
| Date: | 2006-12-03 01:31:37 |
| Message-ID: | 1165109498.25316.15.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, 2006-12-03 at 02:53 +0200, Alexandru Coseru wrote:
> Hello..
>
> Thanks for the tip , i think i have got the ideea..
>
> I'm too tired too , and i will try it tommorow.
>
>
> Anyway , anybody has a clue why this regex is that CPU intensive ? I did
> not saw the light on my drives blinking , and also vmstat doesn't yeld any
> blocks in or out...
> And how can it be optimized ?
I think it's just that you're running the regex across 5400 or so
elements. at 850 or so milliseconds, that comes out to 150uS for each
comparison. I'd say it's just the number of comparisons that have to be
made that's killing you here.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-12-03 04:05:12 | Re: Regex performance issue |
| Previous Message | Alexandru Coseru | 2006-12-03 00:55:27 | Re: Regex performance issue |