Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Windows API
  4. General Opinion Question

General Opinion Question

Scheduled Pinned Locked Moved Windows API
questioncsharpdesignperformancediscussion
3 Posts 2 Posters 3 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Mikeyyy
    wrote on last edited by
    #1

    I have a simple question that I really don't know the answer to: I have two computers, say computer A and computer B. I want to create a c# winform app that automatically copies files from one of my computer A to computer B every 60 minutes. Does it matter in terms of PERFORMANCE where I install my exe, on computer A or computer B? If I install the exe application on computer B will B's CPU % increase and take more load than if I install on computer A? I know this is a stupid design question, but I'd like as many opinions as possible. All response are welcome, thanks!

    L 1 Reply Last reply
    0
    • M Mikeyyy

      I have a simple question that I really don't know the answer to: I have two computers, say computer A and computer B. I want to create a c# winform app that automatically copies files from one of my computer A to computer B every 60 minutes. Does it matter in terms of PERFORMANCE where I install my exe, on computer A or computer B? If I install the exe application on computer B will B's CPU % increase and take more load than if I install on computer A? I know this is a stupid design question, but I'd like as many opinions as possible. All response are welcome, thanks!

      L Offline
      L Offline
      Luc Pattyn
      wrote on last edited by
      #2

      That isn't a stupid question at all. I don't know the specific answer, i.e. I haven't tried it between two (nearly) similar PCs, however in my experience with many other systems, I can say the pull model is normally faster than the push model, i.e. let the app reside on the side that will remotely read and locally write the data. The reason is simple: when you read the data remotely, the result is either data or some error, nothing else needs exchanging, no handshake is required, etc. Writing remotely would involve sending data and somehow get and process an acknowledgment. The difference between both ways will be small when your communication channel is pretty fast with respect to the systems themselves (i.e. Fast Ethernet and not very fast disks), and/or when you apply asynchronous operations (i.e. acknowledgments coming late don't postpone the next packets). :)

      Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

      Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

      M 1 Reply Last reply
      0
      • L Luc Pattyn

        That isn't a stupid question at all. I don't know the specific answer, i.e. I haven't tried it between two (nearly) similar PCs, however in my experience with many other systems, I can say the pull model is normally faster than the push model, i.e. let the app reside on the side that will remotely read and locally write the data. The reason is simple: when you read the data remotely, the result is either data or some error, nothing else needs exchanging, no handshake is required, etc. Writing remotely would involve sending data and somehow get and process an acknowledgment. The difference between both ways will be small when your communication channel is pretty fast with respect to the systems themselves (i.e. Fast Ethernet and not very fast disks), and/or when you apply asynchronous operations (i.e. acknowledgments coming late don't postpone the next packets). :)

        Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

        Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

        M Offline
        M Offline
        Mikeyyy
        wrote on last edited by
        #3

        Ok perfect, thank you!

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups