IPC분류정보
국가/구분 |
United States(US) Patent
등록
|
국제특허분류(IPC7판) |
|
출원번호 |
US-0386439
(1999-08-31)
|
우선권정보 |
JP-0349669 (1998-12-09); JP-0197763 (1999-07-12) |
발명자
/ 주소 |
- Hirata, Toshiaki
- Takenaka, Yasuo
- Matsumura, Eiji
- Miyake, Shigeru
- Miyazaki, Satoshi
- Urano, Akihiro
|
출원인 / 주소 |
|
대리인 / 주소 |
Antonelli, Terry, Stout & Kraus, LLP
|
인용정보 |
피인용 횟수 :
24 인용 특허 :
10 |
초록
▼
A delay factor in a processing in a job system in which an ordered series of jobs are executed in computers assigned to respective jobs, is efficiently detected, and the delay factor is analyzed in detail by associating it with load information of the computers and a network. An administrative manag
A delay factor in a processing in a job system in which an ordered series of jobs are executed in computers assigned to respective jobs, is efficiently detected, and the delay factor is analyzed in detail by associating it with load information of the computers and a network. An administrative manager computer 201 collects a history of executing a job from each job executing computer 202, and refers to a history of each job, one by one from a job executed later to a job executed earlier, until no delay is detected in a job, for judging a cause of delay in each job. Further, with respect to a job in which delay is detected, load statuses of the other jobs or applications in the computer in which said job is in execution are compared with said job and displayed.
대표청구항
▼
A delay factor in a processing in a job system in which an ordered series of jobs are executed in computers assigned to respective jobs, is efficiently detected, and the delay factor is analyzed in detail by associating it with load information of the computers and a network. An administrative manag
A delay factor in a processing in a job system in which an ordered series of jobs are executed in computers assigned to respective jobs, is efficiently detected, and the delay factor is analyzed in detail by associating it with load information of the computers and a network. An administrative manager computer 201 collects a history of executing a job from each job executing computer 202, and refers to a history of each job, one by one from a job executed later to a job executed earlier, until no delay is detected in a job, for judging a cause of delay in each job. Further, with respect to a job in which delay is detected, load statuses of the other jobs or applications in the computer in which said job is in execution are compared with said job and displayed. being associated with another client and being operative to store information in the memory and transmit information from the memory to the another client; determining when one of the first and second threads requires an additional data block of information; and requesting the additional data block of information from the server using the one of the first and second threads on behalf of the other of the first and second threads while restricting the other of the first and second threads from requesting the additional data block of information from the server. 2. The method of claim 1 further comprising the step of storing the first data block and the second data block of information in a cache. 3. The method of claim 2 further comprising the steps of timestamping the information stored in the cache; and removing information from the cache that exceeds a predetermined cache storage time limit. 4. The method of claim 1, wherein the first thread and the second thread are created in response to receiving multiple concurrent requests. 5. The method of claim 1, wherein the first thread and second thread are both operative as a consumer and a producer. 6. A method for retrieving information from a server for multiple clients, comprising the steps of: creating a plurality of threads associated with clients, wherein at least one of the threads can operate as a producer thread that stores information in a memory and as a consumer thread that transmits information from the memory; determining when a first one of the plurality of threads requires additional information; requesting the additional information from a server using the first one of the plurality of threads as a producer thread on behalf of the other of the plurality of threads while restricting the other of the plurality of threads from requesting the additional information from the server; and transmitting the additional information from the memory using the first one of the plurality of threads as a consumer thread. 7. The method of claim 6 further comprising the step of assigning a second one of the plurality of consumer threads as a producer thread. 8. The method of claim 6 further comprising the step of storing the information received from the server in a cache, wherein the step of transmitting the additional information received from the server comprises the step of transmitting information from the cache to the client associated with the first one of the plurality of consumer threads. 9. The method of claim 8, wherein the information is stored in a data block in the cache. 10. The method of claim 9, wherein the step of determining when the first one of the plurality of consumer threads requires additional information comprises the steps of: selecting the first one a plurality of consumer threads associated with a client which received the last data block of information from the cache; and assigning the selected consumer thread as a producer thread. 11. The method of claim 9 further comprising the steps of: timestamping the information stored in the cache; and removing information from the cache that exceeds a predetermined cache storage time limit. 12. The method of claim 6 further comprising the step of receiving multiple concurrent requests from the multiple clients for the information. 13. A method for sending information to multiple clients from a server, comprising the steps of: creating respective threads for requests for information from the multiple clients, wherein at least one of the threads can operate as a producer thread that stores information received from the server into a memory and as a consumer thread that retrieves information from the memory; determining when one of the threads requires additional information for one of the multiple clients; requesting the additional information from a server using one of the threads as a producer thread on behalf of the other of the threads while restricting the other of the thr eads from requesting the additional information from the server; receiving the additional information from the server in response to the request by the one of the threads that is operating as the producer thread; storing the additional information in the memory using the one of the threads as the producer thread; for each client, retrieving the additional information from the memory using respective threads associated with each client as consumer threads. 14. The method of claim 13, wherein the step of determining when the one of the consumer threads requires additional information comprises the steps of: selecting the one of the consumer thread associated with a client which received the end of the information retrieved from the server; and assigning the selected one of the consumer threads as the producer thread. 15. The method of claim 13 further comprising the step of placing the received information from the server in a cache. 16. The method of claim 15, wherein the information is placed within data blocks in the cache. 17. The method of claim 16 further comprising the steps of: timestamping the information placed in the cache; and removing information from the cache that exceeds a predetermined cache storage time limit. 18. The method of claim 15, wherein each client retrieving data from the cache retrieves data from the cache independently of other clients. 19. The method of claim 18, wherein the step of requesting the additional information from the server using the one of the consumer threads as a producer thread comprises the step of synchronizing the request for additional information from the server with operations of other consumer threads. 20. A method of retrieving information from a server for multiple clients, comprising the steps of: creating a plurality of respective threads each associated with a client and operative to function as a consumer that retrieves information from a cache and a producer that stores information in the cache; requesting a data block of information from the server using a first one of the plurality of threads; storing the data block received from the server in a cache using the first one of the plurality of threads as a producer; transmitting the data block of information from the cache to a first client using the first one of the plurality of threads as a consumer; requesting a second data block of information from the server using a second one of the plurality of threads; storing the second data block of information from the server in the cache using the second one of the plurality of threads as a producer; determining when one of the first one and second one of the plurality of threads requires an additional data block of information from the server based on a status of the cache; and requesting the additional data block of information using the one of the first one and second one of the plurality of threads as a producer on behalf of the other of the plurality of threads while restricting the other of the first one and second one of the plurality of threads from requesting the additional data block of information. 21. The method of claim 20 further comprising the step of transmitting the second data block of information to the first client using the first one of the plurality of threads. 22. The method of claim 20 further comprising the step of receiving multiple concurrent requests by the multiple clients. 23. The method of claim 20, wherein the thread used as a producer is associated with the client which received the last data block of information in the cache. 24. The method of claim 20 further comprising the steps of: timestamping the information stored in the cache; and removing information from the cache that exceeds a predetermined cache storage time limit. 25. A data processing system for retrieving information from a server for multiple client requests, comprising: a memory containing: a cache entry for storing information, and a thread processing component that creates a plurality of respective threads each associated with a client, wherein each thread is operative to function as a producer thread that stores information in the memory and a consumer thread that retrieves information from the memory; assigns a first one of the plurality of the threads as a producer thread; requests information from a server using the first one of the plurality of the threads as the producer thread, and transmits information received from the server to a client using the first one of the plurality of threads as a consumer thread; determines when the first one of the plurality of threads requires additional information from the server; requests the additional information from the server using the first one of the plurality of threads as the producer thread on behalf of the other of the plurality of threads while restricting the other of the plurality of threads from requesting the additional information from the server; and a processor for running the thread processing component. 26. A computer readable medium containing computer-executable instructions for receiving information from a server for a client to perform a method, comprising the steps of: creating a first thread associated with a request by the client for information from the server, wherein the first thread stores information in a memory and transmits information from the memory to the client; using the first thread, storing a first data block of the requested information from the server into the memory; transmitting the first data block of information to the client using the first thread; transmitting a second data block of information to the client using the first thread, wherein the second data block was stored into the memory using a second thread, the second thread being associated with another client and being operative to store information in the memory and transmit information from the memory to the another client; determining when one of the first and second threads requires an additional data block of information; and requesting the additional data block from the server using the one of the first and second threads on behalf of the other of the first and second threads while restricting the other of the first and second threads from requesting the additional data block of information. 27. An apparatus for receiving information from a server for a client, comprising: means for creating a first thread associated with a request by the client for information from the server, wherein the first thread stores information in a memory and transmits information from the memory to the client; means for storing a first data block of the requested information from the server into the memory; means for transmitting the first data block of information to the client; means for transmitting a second data block of information to the client using the first thread, wherein the second data block was stored into the memory using a second thread, the second thread being associated with another client and being operative to store information in the memory and transmit information from the memory to the another client; means for determining when one of the first and second threads requires an additional data block of information; and means for requesting the additional data block from the server using the one of the first and second threads on behalf of the other of the first and second threads while restricting the other of the first and second threads from requesting the additional data block of information. of the network.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.