Flex remoting vs. http

[Former Community Member]

I set up a bunch of components using the http requests and
displaying the returned data in data grids. I started changing them
all to use remoting with the turnkey blazeDS since it is supposed
to be so much quicker.



As I was doing so I noticed the components I changed to
remoting were coming back slower than those still in http. So I set
up a test with duplicate components. One on remoting and one on
http. The http kicks it butt every time. I increased the record
count from 8 records to 8000 records and http was still faster.



The only thing I can think of is that I have something set up
screwy. I went through the Cairngorm videos and set the whole thing
up that way but I'm not seeing anything wrong.



Has anyone else experienced remoting slower than http? If so
why?

[Former Community Member]

No takers? I'd hate to abandon remoting just because I don't
know what I'm doing. But in the interest of speed I'll have to go
with http if I can't figure this out. I know remoting wins hands
down according to everything I've read(Although the Flex Bible
qualifies it with "in most cases").

[Michael_Borbor]

Hi there, cairngorm isn't necessary for the remoting.
Remoting is almost always gonna be faster except in some cases when
the remoting adds overhead by the way it works. If you wanna see
metrics about http service vs remoting you can take a look at
http://www.jamesward.com/census/,
and if you wanna know more about performance issues and tuning I
strongly recommend you to watch James Ward's 08 Max Session Working
with Data in Flex