Re: Speeding Up Queries with LINQ

[Mike <koldark@xxxxxxxxx>]

I agree on the speed, but I can manage with 15 seconds. The whole process is
to grab data from SQL Server, send to iSeries, process data with (mostly)
existing RPG logic, grab PDF copies of generated reports and save to file
server, grab calculated data from iSeries and bring back to SQL Server. A
few seconds is nothing in this whole process. Of course I will still work to
make that as quick as possible.

I'll put it this way, we (as in *not* IT) bought a fleet management/asset
management software package that doesn't do the accounting side of fleet.
So, I am now writing that portion. FUN! This windows form application is
the middle-ware to join the two together. My goal is to have it so the users
won't have to deal with the iSeries to run the accounting portion of this
processing.

--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark


On Thu, Mar 11, 2010 at 11:37 AM, Walden H. Leverich <
WaldenL@xxxxxxxxxxxxxxx> wrote:

> Wow! Even 15 seconds is crazy unless that's one really complex statement.
> Or is that 15 seconds for the "job" to run. Still seems long. Glad it's
> improved though.
>
> -Walden
>
> PS. FWIW, I'm a fan of LINQ to object, but not so much LINQ to sql. If it's
> already in memory, LINQ is cool, but it's too abstracted from the DB for my
> liking to use it to retrieve data from the db.
>
>
> --
> Walden H Leverich III
> Tech Software &
> BEC - IRBManager
> (516) 627-3800 x3051
> WaldenL@xxxxxxxxxxxxxxx
> http://www.TechSoftInc.com
> http://www.IRBManager.com
>
> Quiquid latine dictum sit altum viditur.
> (Whatever is said in Latin seems profound.)
>
> -----Original Message-----
> From: systemidotnet-bounces@xxxxxxxxxxxx [mailto:
> systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Mike
> Sent: Thursday, March 11, 2010 11:52 AM
> To: .net use with the System i
> Subject: Re: [SystemiDotNet] Speeding Up Queries with LINQ
>
> An update to this.
>
> It appears like the database was poorly designed. Whatever LINQ was
> generating in the background it was highly inefficient code. I am not
> saying
> the LINQ is bad, it just was bad for this database. I converted to a
> quickly
> thrown together .XSD setup and the processing time went from 1.25 minutes
> to
> 15 seconds. Once I do a proper redesign, I can only guess I'll shave a few
> more seconds off of that. I'll try LINQ again some other day on a better
> database.
>
> --
> Mike Wills
> http://mikewills.info
> P: (507) 933-0880 | Skype: koldark
> --
> This is the .net use with the System i (SystemiDotNet) mailing list
> To post a message email: SystemiDotNet@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
> or email: SystemiDotNet-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/systemidotnet.
> --
> This is the .net use with the System i (SystemiDotNet) mailing list
> To post a message email: SystemiDotNet@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
> or email: SystemiDotNet-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/systemidotnet.